<div>Thank you Matthias.</div>
<div>�</div>
<div>If this class is known to *not* be threadsafe, why is there a "synchronized" statement in primitiveCall? It somewhat confuses me.</div>
<div>�</div>
<div>John<br><br></div>
<div class="gmail_quote">2011/11/20 Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com">matthias@rabbitmq.com</a>></span><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div class="im">On 18/11/11 13:42, john doe wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Is this class threadsafe? I guess not because channels are not threadsafe?<br></blockquote><br></div>Correct.
<div class="im"><br><br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Why is the routing key a final attribute? Why is it not a parameter of<br>primitiveCall(...)?<br></blockquote>
<br></div>The idea is that you create RpcClients to talk to specific rpc servers. The latter are typically identified by a combination of exchange and routing key.<br><font color="#888888"><br>Matthias.<br></font></blockquote>
</div><br>