anonymous wrote : What does 'invm' transport refer to here? Do you want Netty to add in-vm transport, or do you want Netty can talk to the in-vm transport that JBM uses internally? The only interfaces that you need to implement is 'ChannelFactory' and 'Channel', so it's not a big deal to implement a bridge between JBM invm transport and Netty. ClientBootstrap should work with any ChannelFactory implementation. By invm transport I mean rather than writing to a socket channel use an invm channel and pass the buffers directly thus avoiding the latency Tim was talking about. I guess you've answered my question there isn't. So I guess I need to provide a new implementation of ChannelFactory and Channel which can do this? anonymous wrote : I think Netty needs to provide a cookie encoder / decoder as we did for query strings. Ok, this should be pretty simple. anonymous wrote : I understood how it works, but out of curiosity, why does the Servlet need to talk to JBM via Netty? Isn't it just enough for the Servlet to talk to JBM directly? Perhaps I am missing out something. No, JBM will only receive the http response, it won't talk to netty. anonymous wrote : It could be distributed as a separate WAR, hence we could create a subproject under svn.jboss.org/repos/netty/subproject/servlet (or some cool name :-) Ok, that will give it seperation and make it easier to deploy. what would you like to call the sub project? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4201649#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...