[rabbitmq-discuss] share a pre-built queue

Tim Watson watson.timothy at gmail.com
Thu Oct 4 06:56:08 BST 2012


Please keep the list on cc.

On 3 Oct 2012, at 21:37, Prabodh Upreti <prabodh.upreti at vce.com> wrote:

> Tim,
> Thanks for the response. Yes, I am using a topic exchange and routing keys
> as describes in the manual.  Only thing I am doing different is pre-creating
> the queues and letting the consumers bind to those queues.  I have looked at
> a lot of threads and docs and can't find a way to solve this problem in a
> simple way.  

Is there a problem creating a new temporary queue for each client and binding this to the topic exchange using the routing keys that client cares about? I can't imagine you'd do anything dissimilar with another messaging stack (like jms) but perhaps I'm missing something.

What you get with this approach is zero queue maintainable overhead, as the client declares an anonymous, temporary queue that lasts only for the duration of that client's session. The only thing that needs to be pre-built is the exchange, but of course instead of the clients knowing the queue name(s) they know the routing/binding keys instead.

> thank you.
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/share-a-pre-built-queue-tp22319p22327.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

More information about the rabbitmq-discuss mailing list