Seems we're converging towards "do it outside Remoting first and integrate later" or just straight "do it inside Remoting". The multiplexed (bidirectional) transport is the highest priority and also it's possible to tackle it "inside Remoting". Here is a dedicated discussion thread. I've summarized the discussions so far, and I added some suggestions and questions: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3979219 The server-side thread-per-connection issue is something that 1) is being worked on by Tom and 2) requires further discussions as where is actually the cut-off line where an asynchronous solution is really necessary. Please read and comment here http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3979220. The "true" client-side asynchronous calls seem to be also taken care of already. Here is the summary, with some additional open issues: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3979221 The control of the wire format seems to be the really difficult one, in the context of the actual Remoting. This is the dedicated thread: http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3979222. Need more input there. Tim wrote : | At the end of the day we want to build the best messaging system out there and don't want to be prevented from this goal because of this. | Amen to that :) View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979223#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...