<div dir="ltr">On Mon, Sep 23, 2013 at 3:41 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
What are you trying to do?<br></blockquote><div><br></div><div>I want to have a plugin that works with a concept of topics and partitioned queues. What does this mean?</div><div><br></div><div>I want to create a topic called "my_topic" which implies having a consistent hash exchange (CHE) called "my_topic" + one queue called "node_name.my_topic" bound to the my_topic exchange. The queue message contents should live in the "node_name" node.</div>
<div><br></div><div>Whenever a node joins the cluster, I want to automatically declare a queue called "new_node.my_topic" and bind it to the "my_topic" CHE. That queue will be declared on new_node, so the message contents would end up in that node.</div>
<div><br></div><div>With this I want to achieve some sort of "partitioned queues".</div><div><br></div><div>I plan this plugin to be an extension to the management plugin, so one would create one of these topics via an HTTP call.</div>
<div><br></div><div>Also when connecting to a broker, one could ask this plugin via HTTP to send the proper queue name for a particular topic, in order to consume from it.</div><div><br></div><div>Does this makes sense?</div>
<div><br></div><div><br></div></div></div></div>