James Todd wrote:
in working with the avro java rpc server code, it appears to me that
one should be sure to wrap around (and delegate to)
the o.a.a.ipc.Responder.responde(List<ByteBuffer> buffers) method to
ensure application/protocol compliance/leverage/etc.
i came to this (rather quick) conclusion after inspecting the
SocketServer javadoc warnings which led me to the o.a.a.ipc.HttpServer
(jetty) impl that in turn delegates to the ResponderServlet which
largely delegates to the backing Responder.respond().
James,
This sounds right. A server implementation should accept a Responder as
a parameter, and call its #respond(List<ByteBuffer>) method with each
request. The List<ByteBuffer> corresponds to the frames of the request
and the returned List<ByteBuffer> will be used for the frames of the
response.
http://hadoop.apache.org/avro/docs/current/spec.html#Message+Framing
Doug
