[rabbitmq-discuss] Can I get this behavior through a custom plugin?

[Dan Larkin]

Hi all,

I have an interesting serialization requirement for my app:  I need to enforce that only one message with the same AMQP header "client" is ever out for delivery in any given snapshot of time.

Right now I have messages flowing into rabbit to a "direct" exchange, all with "client" headers. And since I have multiple worker nodes pulling from the queue they're ending up in, it's possible for two messages with the same "client" header to be processed at the same time. And the goal here is to prevent that from happening.

I thought at first this might be possible with a custom exchange, but afaict exchanges are basically limited to controlling how messages get routed, not how they get delivered.

So my question is simply:  is this behavior possible?

Thanks for your help,
Dan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20131020/706f81ae/attachment.pgp>