you can tie the txn from qpid to the txn in the DB. This is how it was done in the first store implementation when built on BDB. Then most of the TPL stuff falls away, but it
will be slow. Carl. Steve Huston wrote:
I've been studying the Red Hat message store code and, in particular this week, the transaction handling and TPL. From what I understand at this point, the role of the TPL is to enable recover prepared but not committed transaction actions. And, this is mostly needed because the journal is not transactional. Is this correct? If this is correct, and I am looking primarily at providing an SQL-backed store for Windows (at least right now), I don't really need to worry about the TPL stuff (yet) since SQL transactions don't require an external assist in the form of the TPL. If I use two layers of transaction, one around the 2PC prepare/commit sequence, and others around the individual enqueue/dequeue ops, that would do it, I think. Does this make sense? Thanks, -Steve --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
