[jboss-dev-forums] [Design of JBoss Remoting, Unified Invokers] - Re: R3 transports to implement

[trustin]

So.. the overall architecture could look like this:


  |       +-----------------------------------------------------+
  |   R3: | XNIO-based protocol implementation (R2-compatible?) |
  |       +---------------------+-------------------------------+
  | XNIO: |         SSH         | Custom multichannel transport |
  |       +---------------------+-------------------------------+
  | 

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:


  | R2 client -> R3 endpoint -> R2Req-to-R3Req converter -> Request Listener -> ..
  | .. -> R3Res-to-R2Res converter -> R3 endpoint -> R2 client
  | 

In case of R3 connection, it's simpler:


  | R3 client -> R3 endpoint -> RequestListener -> R3 endpoint -> R3 client
  | 

Please let me know if there's any possible technical difficulties or flaws in implementing this.  I might have completely misunderstood David's idea.  :)

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4166855#4166855

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4166855