[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906919#action_12906919
]
Aaron T. Myers commented on THRIFT-876:
---------------------------------------
bq. Maybe I'm just being dense today, but why would the transport factory get
invoked more than once for a given underlying transport?
It's because the TServer implementations support having different transports
for input and output. See TThreadPoolServer.java:247-248. Even if you only pass
in a single TTransportFactory, the server still calls getTransport() twice.
bq. If that is a must-have, then you might be better off always doing the get()
first thing then checking if it's null rather than doing a contains() call, as
in essence that will lead to two gets for every call.
Thought about doing that. This seemed cleaner. Will change it in the
forthcoming patch.
> 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-876.txt.5, thrift-876.txt.6, thrift-sasl-spec.txt, 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.
