[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904032#action_12904032
]
Todd Lipcon commented on THRIFT-876:
------------------------------------
dreiss and I chatted briefly on IRC and he clarified what he meant above by
"add-on component". The distinction here is one of classification - ie we add a
document somewhere that enumerates (a) the "core" features that every language
implementation must have to be considered "complete", and (b) the "add-on"
features that some implementations choose to implement. The "core" features
would be things like TBinaryProtocol and a Socket transport. The add-on
features would be things like zlib, JSON protocol, HTTP transport, SASL
security, etc. The two types of features would live in the same place in the
code - we're just making clear to the users that if they use an "add-on"
feature it may not be supported by their favorite boutique language.
> 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
>
>
> 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.
