The AMQP gem in ruby can also subscribe to multiple queues using a single thread.<br><br><div class="gmail_quote">On Fri, Jun 10, 2011 at 6:00 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Pierre-Marie,<div class="im"><br>
<br>
On 10/06/11 11:15, PADIOU Pierre-Marie (MORPHO) wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
For now, the only solution I see would be to create as many queues as requests<br>
types (queueA, queueB, etc), and make consumer listen to the appropriate<br>
queues.<br>
<br>
Thing is:<br>
<br>
- this implies that consumers create as many threads as queues there are<br>
listening from (more than a hundred in my case), which I would like to<br>
avoid.<br>
</blockquote>
<br></div>
Which client are you using? Java? If so, a single consumer thread can happily consume from multiple queues. E.g. you can pass a single QueuingConsumer instance to multiple ch.basicConsume(...) invocations.<br>
<br>
<br>
Regards,<br><font color="#888888">
<br>
Matthias.</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
</div></div></blockquote></div><br>