[rabbitmq-discuss] question on exchange type
0x6e6562 at gmail.com
Mon Feb 2 23:55:37 GMT 2009
On Mon, Feb 2, 2009 at 10:59 PM, Mark Geib <mark.geib at echostar.com> wrote:
> The system I am building is, from the amqp broker point of view at least,
> very producer oriented for sure. What is vital is that a producer can safely
> hand off a message to the broker, knowing that at some time a consumer will
> get it. That is, once the message is published the responsibility of that
> message is moved to the broker...even if no consumer currently exists. The
> issue I am struggling with is that if I have to create and bind a queue in
> the producer to make this happen then I have already routed the message.
> This eliminates what consumers can do in the way of 'subscribing' to
> exchanges to have messages routed to it.
Another variant make to route messages to a catch-all queue and then
use a message selector as a predicate for subscriptions. That way you
don't loose any messages and the consumer can still pick and choose.
The selector is, of course, currently just vaporware :-(
More information about the rabbitmq-discuss