[ 
https://issues.apache.org/jira/browse/HADOOP-9820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13731234#comment-13731234
 ] 

Daryn Sharp commented on HADOOP-9820:
-------------------------------------

bq.  Since SaslRpcInputStream is only used when sasl-wrapped, shouldn't it 
throw an exception if the callId is not SASL.callId?

I did consider if an exception should be thrown.  However, it would preclude 
the server sending any control messages to a given session.  Non-SASL messages 
might be something like a server sent ping to see if the client session is 
still alive.  Or maybe to forcibly close the session, etc.  I erred on the side 
of future flexibility.  Thoughts?
                
> RPCv9 wire protocol is insufficient to support multiplexing
> -----------------------------------------------------------
>
>                 Key: HADOOP-9820
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9820
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: ipc, security
>    Affects Versions: 3.0.0, 2.1.0-beta
>            Reporter: Daryn Sharp
>            Assignee: Daryn Sharp
>            Priority: Blocker
>         Attachments: HADOOP-9820.patch
>
>
> RPCv9 is intended to allow future support of multiplexing.  This requires all 
> wire messages to be tagged with a RPC header so a demux can decode and route 
> the messages accordingly.
> RPC ping packets and SASL QOP wrapped data is known to not be tagged with a 
> header.

--
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

Reply via email to