[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13666735#comment-13666735
]
Daryn Sharp commented on HADOOP-9421:
-------------------------------------
Out-of-sync issues are inevitable if the client or server goes into a specific
mode where it assumes a specific protobuf. Ie. How does a secure client know
if it will get a RPC failure or SASL response after it sends the connection
header? How can you fix the bad version response to handle that?
Simply wrapping the sasl protobufs like other rpc calls allows the
client/server to know how to decode the subsequent protbuf message. I don't
feel it's a hack so much as good design. If this is our foreseeable last
chance to modify RPC, then we need to make rpc decoding as flexible as possible.
> 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-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
