"ovidiu.feodorov(a)jboss.com" wrote : | | As far as I remember, the current code relies on the fact that it receives an acknowledgment (in the form of an exception NOT being thrown) for each server->client delivery. | | Sure, the current code uses RPC, we don't have a choice with the version of remoting we are using, that's the only reason it's that way. But it is unnecessary. Actually we can radically simplify the server consumer endpoint message dispatch if we go async - no need for the deliverer or any of that stuff any more - less context switches etc anonymous wrote : | Well, in this case AMQP has a problem if it doesn't also provide for synchronous client-to-server delivery. Need to hit the books, to make sure this is (or not) the case. | I think AMQP supports both sync AND async. I need to hit the books too :) anonymous wrote : | Right. So ConnectionEnpoint.sendTransaction() IS a RPC. | It is. Did I say otherwise? anonymous wrote : | We're clear. We need both. And this needs to be reflected in the Remoting API. I'll soon add the document with the proposed changes. | Cool View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3979589#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...