[rabbitmq-discuss] Performance of "blocking publisher-confirms" vs. transactions

[Matt Pietrek]

As I've detailed in other posts to this DL (http://bit.ly/zf6sKC), we have
situation where straightforward publisher-confirms aren't appropriate in our
scenario. We need to know the broker has received the message, and we have
to assume our client can die at any moment, so retransmitting messages is
not an option for us.

What I'd like to know is: Is there any benefit to creating our own "blocking
publisher-confirm publishing"? That is, we'd do the following:

Publish a single message
Block on an event 'X'
When the publisher confirm comes in, signal 'X'
Return from the publish call

In a mirrored queue scenario, is there any advantage to doing this vs. using
straight-up transactions?

Matt

p.s. I realize in the above pseudocode that multiple threads would be
necessary - One to block and the other to listen for the publisher-confirm.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20120216/6060b93d/attachment.htm>