Hi camel-netty producer is now async as well.
However I wonder if NettyConsumer should be async as well? We do have the Channel in which a reply should be send back to, which allows us to use it from the async callback. Which should allow the NettyConsumer thread to return and let Netty reuse that thread to service new requests. I am just wondering if keeping that Channel around longer than the original request thread would cause any issues? I was looking for continuations support in Netty but there is no such thing currently. This would obviously make it a first class feature in Netty and make me more comfortable to let the continuations handle returning the reply when the async routing is done. -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
