Hi, As you know Netty[1] provides excellent supports of NIO and you can still get the full control of protocol handler. It could be useful if we provides a Netty transport of CXF.
I just did a prototype of support Netty transport for CXF, it include the server side implementation and client side implementation. And I did some performance compare tests by running the wsdl_first from examples with Jetty transport and Netty transport and using Jmeter to send the requests. The test results are much similar, Netty transport and Jetty transport can hit the highest processing recorder with the throughput of 9M per second in my MacBookPro. I only performance turning I did was just changing the thread pool size of ExecutionHandler which will be used to call the whole soap stake of CXF. I'd like to commit the prototype into Apache CXF trunk, and we could polish the transport together :) Any thought? [1]http://netty.io/ -- Willem Jiang Red Hat, Inc. FuseSource is now part of Red Hat Web: http://www.fusesource.com | http://www.redhat.com Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) (English) http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) Twitter: willemjiang Weibo: 姜宁willem
