"trustin" wrote : I think we can make the XNIO-based protocol implementation look similar to that of Remoting 2 socket transport. As David explained in the IRC channel, we could simply retain the core classes which are serialized and deserialized in R2 and convert them to R3 classes and vice versa to implement R2 compatibility: This would be a problem due to the fundamental difference with how R2 requests are made. I don't think that the R2 version will have much similarity to R3 because the R2 marshaling and protocol format are very limited. Like Tim pointed out in a more recent post, R3 should not accept the same basic limitations at its core. A bit later I'll post a diagram illustrating how the various bits might work together. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167018#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...