<div>Hi Matthias,</div><div><br><div class="gmail_quote">
On Fri, Feb 15, 2013 at 12:48 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Jonathan,<br>
<br>
On 15/02/13 20:34, Jonathan wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I read that each channel in the Java client gets its own thread.<br>
</blockquote>
<br>
Where did you read that? It's not true.<br></blockquote><div><br></div><div>What I was reading was from here:<div><br></div><div><a href="http://www.rabbitmq.com/api-guide.html#consuming" target="_blank">http://www.rabbitmq.com/api-guide.html#consuming</a></div>
<div><br></div><div>"Each Channel has its own dispatch thread"</div><div><br></div><div>Maybe you could clarify what that means.</div></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Also, what are some strategies for determining how to partition messages<br>
by channel? For example, if I'm routing messages for a set of users in<br>
my application, it's simple to create one channel per user.<br>
</blockquote>
<br>
Nothing wrong with that.</blockquote><div><br></div><div>Good to know.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><font color="#888888"><br>
<br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>