On 01/26/2012 05:50 AM, Rob Godfrey wrote:
Looks interesting...
how do you ensure transactional atomicity with this approach (e.g. on the
primary broker in a transaction I receive from one queue, do work and then
publish to a second queue... if the queues are replicating independently is
it possible to guarantee that in the backup broker you do not have the
condition that the dequeue was replicated but the enqueue was not?)
Currently we don't, it's mentioned in the section on limitations. I think the
solution will be to add extra transactional "event" messages (like the position
event messages that are sent now) and to annotate messages with headers
providing transactional info. It'll be a significant piece of work but I think
its doable.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
