"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: | There's also the non-invocation protocol elements to worry about. That is, in addition to ordinary invocations, org.jboss.remoting.ServerInvoker handles connection monitoring, callbacks, and streaming. But Tim gives me an idea. To my knowledge (and Scott can correct me if I'm wrong :-) ), JBossMessaging is the only JBoss project that uses leasing and callbacks. And since JBM 1 (which lives in EAP 4.2) and JBM 2 (which I assume will live in EAP 5) are not compatible, the need to support these features in the Remoting 2 <-> Remoting 3 compatibility solution plummets in urgency. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4167213#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...