avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (AVRO-641) add SASL to socket transport
Date Thu, 16 Sep 2010 20:36:34 GMT

     [ https://issues.apache.org/jira/browse/AVRO-641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Doug Cutting updated AVRO-641:
------------------------------

    Attachment: AVRO-641.patch

Here's a new version of this patch that I believe is ready to commit.

Changes include:
 - add a status code to each message in the negotiation
 - add the SASL mechanism name to the first negotiation message 
 - transmit a UTF-8 error message when negotiation fails
 - stop double-framing transmitted data
 - optimize framing of non-QOP data at write, merging small frames, reducing packets and read
system calls
 - use gathered writes, potentially reducing write system calls
 - add a document describing Avro's SASL profile


> add SASL to socket transport
> ----------------------------
>
>                 Key: AVRO-641
>                 URL: https://issues.apache.org/jira/browse/AVRO-641
>             Project: Avro
>          Issue Type: New Feature
>          Components: java
>            Reporter: Doug Cutting
>            Assignee: Doug Cutting
>             Fix For: 1.4.1
>
>         Attachments: AVRO-641.patch, AVRO-641.patch, AVRO-641.patch, AVRO-641.patch,
AVRO-641.patch, AVRO-641.patch
>
>
> Java's socket transport is non-standard (not in the Avro spec) but might serve as a prototype
of a future standard transport (AVRO-341).
> It would be useful to extend it to support SASL-based authentication and encryption.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message