Hi, jdepp:<br><br><div class="gmail_quote">On Mon, Jan 14, 2013 at 10:43 AM, jdepp <span dir="ltr"><<a href="mailto:j_depp_99@yahoo.com" target="_blank">j_depp_99@yahoo.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
if you don't mind me asking a couple more just based on definitions - how is<br>
the routing key associated with a queue; is it just a sort of identifier to<br>
pass a msg to a specific queue?<br>
Sort of attaching a label (routing key) to a paper that needs to be filed<br>
and the queue is the folder that will hold the paper.<br>
Also what exactly is the virtual host for then within a broker. I am sorry<br>
about these questions, but I get a better understanding when explained in<br>
simple words.<br></blockquote><div><br></div><div>The tutorials here should clarify some things: �</div><div><br></div><div><a href="http://www.rabbitmq.com/getstarted.html">http://www.rabbitmq.com/getstarted.html</a></div>
<div><br></div><div>Your understanding of routing keys is in the ballpark. �In brief:</div><div><br></div><div>A producer publishes to *exchanges*. �Queues are bound to exchanges and these queues will receive messages published to the bound exchange depending on:</div>
<div><ol><li>The type of the exchange</li><li>The routing key used on message (if appropriate for exchange type)</li><li>The binding key associated with the binding of the queue to the exchange</li></ol><div>The tutorial examples show you the behaviors of a couple of different exchange types and how they interact with routing and binding keys. �In particular the "publish/subscribe," "routing," and "topics" examples show how choice of exchange type and keys support fairly rich and flexible routing of your messages.</div>
</div><div><br></div><div>A virtual host is just a way of partitioning up the resources of a RabbitMQ broker. �Users can be given access to particular vhosts, and a given vhost provides a sealed namespace fo the queues/exchanges/routings/etc. that exist within it. �Thus queue "q_foo" in vhost "host_blah" and "q_foo" in vhost "host_blarg" are different entities, with access to them governed separately.</div>
<div><br></div><div><br></div><div><br></div></div>