I think it is reasonable to push for the consensus on these issues, at
least with respect to spec and direction, for 1.7.0. This will require a
push amongst us volunteers to complete a concrete implementation and spec.
Cross-language asynchronous, out-of-order RPC is an important piece of
the Avro puzzle.
This is one of the larger open issues in the community. I am willing to
host an Avro developer meeting to discuss this and other nominated issues
if the community feels that would be useful. (Downtown San Francisco /
On 3/4/12 3:56 PM, "Mike Percy" <[EMAIL PROTECTED]> wrote:
>Hi Avro devs,
>What is the latest on Avro RPC interoperability? Flume 1.x is currently
>using the Avro Netty implementation as an RPC protocol, however I am not
>aware of compatible implementations of this transport in languages other
>than Java  and I wonder if this protocol will ever be compatible 
>with a future standard .
>Would any of you folks recommend running RPC APIs intended for public
>consumption on top of NettyServer at this time? It seems to be the one
>with the most active development going on, and appears to have
>significant interest, which is a good sign. Since there are other RPC
>transports available as well - SaslSocketServer and HttpServer - I am
>also wondering what anecdotal experience others can share about these
>implementations, in terms of speed, interoperability, and maturity.
>Thanks in advance for your thoughts.
> https://issues.apache.org/jira/browse/AVRO-341 - specify avro
>transport in spec