<div dir="ltr">On Thu, Jul 18, 2013 at 2:52 PM, David van Geest <span dir="ltr"><<a href="mailto:davidv@spindance.com" target="_blank">davidv@spindance.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Hi,<div><br></div><div>I've been looking at the�<a href="https://github.com/rabbitmq/rabbitmq-mqtt" target="_blank">https://github.com/rabbitmq/rabbitmq-mqtt</a>�plugin. �It states in the README that:</div>
<div><br></div>
<div>"The exchange is expected to be an AMQP topic exchange."</div><div><br></div><div>Is there any reason it could not be a direct exchange, or a custom exchange such as this:�<a href="https://github.com/jbrisbin/random-exchange" target="_blank">https://github.com/jbrisbin/random-exchange</a>.</div>
<div><br></div><div>Clearly the MQTT PUBLISH topic would be unused in this case, but I don't necessarily care about it.</div><div><br></div></div></blockquote><div><br></div><div>Thinking about this a little more, I really would not want to lose the ability to do topic publishing in MQTT. �Fortunately, it seems there's another way. �With Rabbit's Exchange-to-Exchange bindings (<a href="http://www.rabbitmq.com/blog/2010/10/19/exchange-to-exchange-bindings/">http://www.rabbitmq.com/blog/2010/10/19/exchange-to-exchange-bindings/</a>), it seems that MQTT messages could first go to a topic exchange, and then based on exchange-to-exchange bindings, be routed to a custom exchange (such as the random one above).</div>
<div><br></div><div>Any reason this wouldn't work? �Am I really off in the weeds?</div></div>
</div></div>