I see that the HTTP RPC on all platforms implement the message framing described in the Avro specification. However, the java Netty implementation framing is a bit different. Specifically:
1) It prepends an 8 byte header to each request/response which encodes a call id and the number of frames to follow. 2) It uses the number of frames value above to decide when to stop reading as opposed to writing a zero length frame. >From what I can tell that protocol is unique, e.g. a Netty client can only >talk to Netty server (java to java). I'm wondering what is the plan for supporting this? Will plain socket implementations on other platforms implement this or something else? Thanks, Shaun
