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-707) promote Sasl-based RPC
Date Wed, 08 Dec 2010 22:58:01 GMT

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

Doug Cutting updated AVRO-707:
------------------------------

    Attachment: AVRO-707.patch

Here's a patch for this.  Change are:
 - Two new static factory methods that understand "http:" and "avro:" URIs, using SaslSocket
for "avro:":
   --  Transceiver Ipc.createTransceiver(URI)
   --  Server Ipc.createServer(Responder, URI)
 - switches the rpcsend and rpcreceive tools to use the new factory methods
 - deprecates SocketServer and SocketTransceiver in favor of SaslSocketServer and SaslSocketTransceiver



> promote Sasl-based RPC
> ----------------------
>
>                 Key: AVRO-707
>                 URL: https://issues.apache.org/jira/browse/AVRO-707
>             Project: Avro
>          Issue Type: Improvement
>          Components: java
>            Reporter: Doug Cutting
>             Fix For: 1.5.0
>
>         Attachments: AVRO-707.patch
>
>
> SaslSocketTransceiver and SaslSocketServer should be preferred to SocketTransceiver and
SocketServer.  The former are more optimized and offer the option of security. The latter
should be deprecated to discourage a proliferation of implementations.
> We should also add Transceiver and Server factory methods that accept a URI.  For "http:"
URIs these should use HttpTransceiver and HttpServer.  For "avro:" URIs these should use SaslSocketTransceiver
and SaslSocketServer.  The rpcsend and rpcrecieve tools should use these factories.

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