The rabbitmq-c doesn't provide much of an API for dealing with multiple consumers (or heck the API for dealing with consuming from one consumer is tedious at best). �That said if you're willing as a programmer to deal with the library at a low level (mostly keeping track of frames that are�received�from different amqp channels) there is nothing in the rabbitmq-c library that prevents multiple consumers to be used.<div>
<br></div><div>-Alan<br><br><div class="gmail_quote">On Thu, Mar 8, 2012 at 12:05 PM, Eric J. Holtman <span dir="ltr"><<a href="mailto:eric@holtmans.com">eric@holtmans.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 3/8/2012 11:00 AM, Alan Antonuk wrote:<br>
><br>
> To clarify: It is safe and reliable to have more than one consumer per<br>
> AmqpClient::Channel object.<br>
><br>
<br>
</div>I thought this was not the case, since the underlying<br>
C library didn't support it. �Quite willing to be wrong<br>
there.<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">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></div>