JBoss Messaging uses JBoss Remoting to provide the client-server and server-client communication and uses jgroups to provide the clustering capabilities.
Yes, JBoss Remoting is currently used for client-server communication.
Using NIO is on our roadmap and we are currently looking at various ways to implement this.
JBoss Remoting 3 plans also to be based on a NIO infrastructure.
There are various options: remoting 3, MINA, grizzly etc. and various combinations of the listed.
If you have any more ideas, please share them :)
Actually I was also considering MINA-like tooleset.
So just to confirm: making JBM NIO based actually means adjusting JJBRemoting NIO based.
Am I right?
Sorry, now I got it.
So, its not decided yet which of the frameworks to use (MINA, Remoting), this is something we should explore.
Initially it's likely we will use the transport layer from QPid to implement our NIO transport, and keep remoting 2.x really just to implement the HTTP transport.
This layer is based on MINA and implements another layer of abstraction that allows you to specify your protocol and it handles the request/response correlation and all that kind of stuff.
Also, apparently we are bringing on Trustin Lee, the author of Apache MINA into JBoss. This is great news, and I imagine this means remoting 3 is going to based on MINA principles and technology.
This means in the mid-long term we can go back to using remoting 3 when it is out, however I doubt whether this will be in the timescales we need. Luckiy though everything will be based on MINA so the transition won't be so bad.
we are bringing on Trustin Lee.
Well, that are good news, and it sure means that now we mortals should watch and learn from the masters how things are done :).
Really looking forward seeing MINA at its best.