[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904743#action_12904743
]
Bryan Duxbury commented on THRIFT-876:
--------------------------------------
I like the proposal.
The way it's described and implemented now, this is an unbuffered transport on
write and a buffered transport on read, which I think will make it hard to use.
What if, instead, we make it buffered on both the write and read side and
basically be a stand-in for the existing TFramedTransport. That would mean that
an entire RPC request or response would fit into a single frame and there'd be
no ambiguity about when messages would be sent (it would happen on flush()).
> Add SASL support
> ----------------
>
> Key: THRIFT-876
> URL: https://issues.apache.org/jira/browse/THRIFT-876
> Project: Thrift
> Issue Type: New Feature
> Components: Java - Library
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Attachments: thrift-876.txt, thrift-876.txt.2, thrift-876.txt.3,
> thrift-sasl-spec.txt
>
>
> It'd be nice if there were some way of securing Thrift communication in a
> pluggable fashion. SASL is the implementation chosen by Hadoop for this.
> Seems like a good option for Thrift, too.
> I'll start with a Java implementation, then move on to support the other
> language bindings.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
