Re: [jboss-dev] Remoting 3.0

Scott M Stark wrote: Actually, a "base asynch message oriented architecture" was just what I was trying to get at. While Remoting should continue to support the rpc model, the Connection.receive() and Connection.send() methods that I mentioned are intended to support asynchronous message sending and receiving. Also, while it's true that client and server roles are inherently asymmetric, actors can play multiple roles (like Peter Sellers). In Remoting, for example, callbacks (in push mode) are handled by clients on the server side talking to servers on the client side. I think the same thing would be conceptually simpler with a "connection" abstraction that mirrors a real TCP connection: it's true that there are client and server sockets, but once the connection has been created, there can be senders and receivers on both sides. The idea of stacks of marshallers and unmarshallers in Remoting has been floating around for a while, and Tom did some initial work in that direction. I'm thinking that's where the layered message handling will live. I've been meaning to write a second document on the subject, but, in fact, MINA has a pretty flexible and sophisticated framework for chains of message handlers, which looks like a good match for what we want. As you say, we need to understand how MINA and Remoting will work together.