oh okay.. thanx for the response guys...<div><br></div><div>Like uve guessed, we do have need for multiple channels. Basically, we have a large number of consumers each listening for messages on their own specific queuus. So for each consumer, we have to create a channel.. and yes.. like uve guessed, we do enforce certain specific qos settings on there channels.. </div>
<div><br></div><div>So is it safe for me to assume, that like Alex mentioned, there should NOT be any issue if I create ALL the channels on the same connection ?</div><div><br></div><div>-Arun</div><div><br><br><div class="gmail_quote">
On Thu, Jul 22, 2010 at 10:34 PM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@rabbitmq.com">matthew@rabbitmq.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 Thu, Jul 22, 2010 at 05:59:53PM +0100, Alexandru Scvortov wrote:<br>
> Otherwise, there shouldn't be any reason to have multiple channels.<br>
<br>
</div>Well, channels are stateful so for example you either have a<br>
transactional channel or a non transactional channel. That's a reason to<br>
have multiple channels. Also if you want different qos settings in<br>
different channels then that's a reason, also the meaning of<br>
ack{multiple=true} is obviously scoped by the non-acked msgs received in<br>
each channel. Thus there are some reasons to have multiple channels. But<br>
generally creating a pool of them or connections is, as Alex says, a bad<br>
idea.<br>
<br>
Matthew<br>
_______________________________________________<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>
</blockquote></div><br></div>