[
https://issues.apache.org/jira/browse/HADOOP-9421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689619#comment-13689619
]
Luke Lu commented on HADOOP-9421:
---------------------------------
bq. I'm referring to the roundtrip your patch introduces by responding with
negotiate if it's a non-token auth.
The roundtrip is mandatory for non-token auth in your patch. It's optional in
mine.
bq. The client can't chose the best auth
Sometimes it's the only choice, eg. delegation token for tasks, which covers
99% of the auth workload in typical clusters.
bq. The roundtrip reduction "hack" is a feature that can be extended to any
sasl mechanism that can initiate.
No it cannot reduce round-trip for SCRAM or Kerberos, while my patch can.
bq. The point you keep missing is the client can't guess an auth method but you
keep focusing on retaining that behavior.
The point you keep missing is that the client initiate proto is free and
optional from network round-trip point of view, which opens door for future
optimization for SCRAM etc.
> 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
> Priority: Blocker
> Attachments: HADOOP-9421.patch, HADOOP-9421.patch, HADOOP-9421.patch,
> HADOOP-9421.patch, HADOOP-9421.patch, 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
