<div>Hi Jerry,</div>
<div>�</div>
<div>thanks for the reply.� That's good news on the multiple bindings.� The more that I get to know RabbitMQ, the more I like it.</div>
<div>�</div>
<div>I'm using the C# .Net client at the moment (might like to add another language client or two in future).</div>
<div>�</div>
<div>I had found the api guide, and faq.� I haven't explored the java library yet. I looked at� + played with the .net examples: declareQueue, perf test, subscriber, etc.� I also looked at a bunch of the presentations�such as the one that Alexis did at Google. BTW: the getting started guide with the python/java examples is quite good.</div>
<div>�</div>
<div>I'm at the stage where I need to solve specific problems / issues + choose an optimum exchange / routing setups. I'm sure you've been there yourself i.e. high level pretty good.�Low level -- like that example was easy, I can see how that worked, but still stumbling around a little bit in the code for my stuff type of thing. Getting there.�If you guys can help me put my hands on some of these specifics I'd appreciate that.</div>
<div>�</div>
<div>thanks,</div>
<div>-Steven<br><br></div>
<div class="gmail_quote">On 10 December 2010 18:59, Jerry Kuch <span dir="ltr"><<a href="mailto:jerryk@vmware.com">jerryk@vmware.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Also, I neglected to mention the tutorials...<br><br><a href="http://www.rabbitmq.com/how.html" target="_blank">http://www.rabbitmq.com/how.html</a><br>
<br>The section "Messaging Patterns and Common Scenarios" contains links to a bunch of messaging patterns and idioms that people have found useful in practice and how to realize them on AMQP/Rabbit.<br><br>Best regards,<br>
Jerry<br>
<div>
<div></div>
<div class="h5"><br>On Dec 10, 2010, at 10:26 AM, Steven Taylor wrote:<br><br>> Hi,<br>><br>> are there any good RMQ examples, or documentation for routing keys?<br>><br>> Essentially, I'd like to have a control stream that can accept broadcasts for all nodes, messages for a type of node, or messages intended for a specific node (or subtype).<br>
><br>> all.category1.nodeType.nodeName<br>><br>> potential routing keys:<br>> all.*<br>> *.nodeType.*<br>> all.category1.nodeType.nodeName � -- full path<br>><br>> On a per node basis, is that three extra channels & 3 extra threads? �OR: I figure it'd be easier if these three routing keys were attached to one queue. Is there a secret comma operator for routing keys that I'm not aware of for use with QueueBind? �If I call QueueBind three times, will the result be cumulative? Are channels expensive on the RMQ server? How about on the client side?<br>
><br>> I'll be testing this, but if someone could provide a little advice it'd be appreciated.<br>><br>> thanks,<br>> -Steven<br></div></div>> <ATT00001..txt><br><br></blockquote></div><br>