My feeling is we shouldn't duplicate effort on this one. We have an urgent need for a NIO transport, but we don't need all the bells and whistles of a generic framework like remoting. I would rather us write our own specific transport in a few weeks then contribute that back to the remoting project where you can add the extra bits and shiny bells and buckles. My feeling is that if you start trying to create an all singing dancing NIO framework now this is going to take too long for us which introduces a major risk for us. Wdyt? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036096#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...