hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Lu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9421) Add full length to SASL response to allow non-blocking readers
Date Tue, 26 Mar 2013 17:53:16 GMT

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

Luke Lu commented on HADOOP-9421:

Current sasl response format:
<v8-sasl-response> ::= <status-int32> (<success-response-length-int32><sasl-token-bytes>|<error-string-length-int32><error-string-bytes>)

I had the following in mind:
<v9-sasl-response> :: = <response-length-int32> <response-protobuf>
<response-protobuf> ::= <status> <optional-token> <optional-error-message>

I think the current format has enough "fixed" prefix to allow non-blocking client but the
reader needs to know the sasl protocol (status etc.). The new proposal will make it consistent
with the rest of the RPC format, which allows a generic non-blocking reader (similar to server
side) to read an opaque response and hand it off to a specific protocol processor.

What do others think?

> 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
>            Reporter: Sanjay Radia

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

View raw message