[
https://issues.apache.org/jira/browse/AVRO-975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13629039#comment-13629039
]
Doug Cutting commented on AVRO-975:
-----------------------------------
Compatibility with SocketTransciever should not be a priority.
NettyTransceiver is probably the most widely deployed format of Avro RPC, but
it does not support authentication and authorization, as does SaslTransceiver.
Long-term we need something that supports both async (like NettyTransceiver)
and security (like SaslTransceiver). We'll likely do this either by extending
NettyTransceiver's format (adding SASL to connection initiation) or extending
SaslTransceiver's format to support async (adding request IDs). Until these
converge, it makes some sense to continue to invest in both. Variety in
formats is the bane of interoperability, and SocketTransciever has no role in
the path to convergence since it supports neither async nor security, so we
should not invest in it further. (See also AVRO-625.)
> Support RPC in C#
> -----------------
>
> Key: AVRO-975
> URL: https://issues.apache.org/jira/browse/AVRO-975
> Project: Avro
> Issue Type: New Feature
> Components: csharp
> Affects Versions: 1.6.1
> Reporter: Jeff Hammerbacher
> Attachments: 975.patch, Avro-975-00.patch, buildtask.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
