[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13639246#comment-13639246
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. Having the client suggest a mechanism is probably less useful because it
won't eliminate a round-trip.
Maybe I'm missing something but it seems straightforward that we'll save extra
round trips if client suggests a mechanism that server supports. e.g. There is
no extra round trip for PLAIN and Digest, while you can have up to n sasl-next
round trips with your proposal if client doesn't support the server mechanisms.
I'd think that it's reasonable to assume that server mechanisms is typically a
superset of that of a client, which typically contains only one
mechanism/protocol.
bq. The token value doesn't necessarily have to be in the config.
I was talking about the mechanism order. Your proposal will need to challenge
the client one mechanism/protocol by one somehow.
> Add full length to SASL response to allow non-blocking readers
> --------------------------------------------------------------
>
> 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: Junping Du
> Attachments: HADOOP-9421.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
