On 04/09/2014 03:28 PM, Chris Richardson wrote:
I've set this scenario up on my test system (I had to add "--argument domain=BrokerB" to the "qpid-config add incoming|outgoing ..." commands...)
Sorry!
and it looks promising, except if I understand correctly there is no queuing on the relaying node since it's a dispatch router. Unfortunately we absolutely need this.
Just to be clear, you would have queueing on either side, and the message would not be dequeued from A before being enqueued at C. However B would not itself accept responsibility, it would relay the acknowledgements, but it wouldn't undertake to deliver a message from A, even if A went away (i.e. no store-and-forward).
[...]
We're obviously very interested in these next developments. Can you give us a rough idea of when we can hope to see these implemented, at least in beta?
Ted would be the best person to answer that, My understanding is that some of the code is already in place on trunk, albeit in a rudimentary form, so its not very far away from some kind of usable alpha I would think.
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
