This is required to support AMQP. Tom Elrod wrote : | It is possible to send and receive raw payload data using remoting where is not wrapped in the remoting InvocationRequest/InvocationResponse using configuration per request. | Right, but this assumes an initial invocation made by a Remoting client. The issue that we have to deal with here is that a completely unknown client (that may be written not even in Java) sends AMQP frames, and Remoting has to parse them, or at least delegate the parsing to a pluggable module. As far as I know, this is beyond of Remoting's capabilities, today. More on this: Tim wrote : | We should bear in mind, that at some point (not too long) we probably need to support the AMQP protocol. The AMQP protocol defines a full wire format protocol down to the last byte. Including the wireformat of the multiplex, heartbeats etc. | I don't see how we would get that to work with remoting. So we would have to do major work then _anyway_. | Some other (valuable) musings: genman wrote : | In my opinion, it's quicker (and oddly pleasant) to craft something out of a formal specification, than to work on your own protocol. How does it go? "Bad artists copy. Great artists steal." | Right. We didn't think to do it otherwise :) genman wrote : | You need a framing protocol, and I would get to work implementing AMQP right away. Then later, or simultaneously, abstract AMQP into one of the JBoss remoting system. | That sounds to me like a suggestion to "do it quick and dirty now and integrate later". The discussion is open. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979222#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...