Tim, I think you should do what you think is right for messaging. As purely personal opinion, I think that remoting should move to a messaging based model (compared to being solely RPC based) for remoting 3. I also think that if this to be the case, remoting should do its best moving forward to support behavior/features other project might need so they can use remoting without having to write/maintain that same code internal to their projects. Of course, this means that end result of remoting 3 would have to be compelling enough (i.e. all the features, behaviors, performance, etc.) that other projects would be willing to adopt it. In order to do this, the remoting team HAS to know and understand the requirements other project have. This why I started this thread. As far as NIO goes, the only real performance gain in using NIO is when you have a very large number of concurrent connections being processed since it does not require a thread per connection and the associated overhead of thread context switching. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4036201#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...