Brian McCallister wrote:
Is the socket server in avro intended as an example/dev option or a productiony server?
It's more of an example. The wire protocol is probably fine for production, but the existing client and server are pretty dumb. There's no connection pooling, async server-side i/o etc.
The Java HTTP-based version performs much better than the socket version in my micro-benchmarks. It gets connection pooling for free, and it's easy to configure it for an async server that can support more connections than threads. Today that's the most production-worthy implementation.
Doug
