[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678288#comment-13678288
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. The IpSerializationType change is orthogonal to this patch, so I'd like to
defer to another jira if that's ok?
Yes. HADOOP-9630
bq. I changed the authMethod in the connection header to specify the
authentication protocol - in this case none, or sasl, to allow for future
protocols. I think that's what you wanted?
I wanted to get rid of the byte completely and let client always do a SASL call
with RpcSaslProto with an initial auth method field, so that the client
initiation is extendable. If you really want to use the byte for auth protocol
NONE vs SASL (and potential other protocols), I'm fine (but change AuthCallId
in the javadoc to AuthProtocol to be consistent). The main thing I'd like to
have is be able to evolve client initiation (to save a round-trip with cached
mechs) without having to change the RPC version again.
> Convert SASL to use ProtoBuf and add lengths for non-blocking processing
> ------------------------------------------------------------------------
>
> Key: HADOOP-9421
> URL: https://issues.apache.org/jira/browse/HADOOP-9421
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 2.0.3-alpha
> Reporter: Sanjay Radia
> Assignee: Daryn Sharp
> Attachments: HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
> HADOOP-9421-v2-demo.patch
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
