[rabbitmq-discuss] ruby amqp gem AMQP::Rebroadcaster feature
m.nacos at gmail.com
Mon Oct 24 08:28:13 BST 2011
exchange-to-exchange bindings are great for complex topic routing -- but
this assumes the routing key for each message is (a) decided on entry and
(b) stays the same throughout a message's flow through the system.
so, what happens if a consumer needs to affect a particular message's route?
e.g. to reinject/rebroadcast invalid/malformed/unauthorized messages into a
different queue/pipeline. Sure, it could change the routing key, but it'd
still need to rebroadcast/reinject, right?
is this kind of flow so exotic? I'd imagine it's a pretty common scenario.
On 23 October 2011 22:29, Michael Klishin <michael.s.klishin at gmail.com>wrote:
> 2011/10/23 Michael Nacos <m.nacos at gmail.com>
>> Has there been any progress? Is this still in the roadmap?
> I don't mind adding this but in practice exchange-to-exchange bindings 
> is a better solution. So I think support for that will come first.
> 1. http://www.rabbitmq.com/extensions.html#exchange-bindings
Want to sign up for websites without giving your email? Ask me for a leemail
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss