[
https://issues.apache.org/jira/browse/THRIFT-876?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904817#action_12904817
]
David Reiss commented on THRIFT-876:
------------------------------------
I don't think that's the same thing. That's necessary for the number to be
transmitted from Thrift to Thrift. The higher-level code doesn't have to
concern itself with that level. We *don't* specify that images should be
transmitted as PNG, though. We just give client code access to the binary type
and let it do whatever it wants. Making a protocol SASL-compliant is all about
providing a way for implementations to pass bytes back and forth. That's what
we should be doing: passing bytes, not putting any interpretation on them.
> 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.
