RabbitMQ supports MQTT, and can do routing of messages between different queues/exchanges, at least for AMQP (where we already use it). This is nice because MsgFlo can stay out of the direct message passing codepaths. If possible, it would be nice to use this also on MQTT.
However, since this is not a part of standard MQTT we likely need to keep our existing own routing code around as well. Probably this will be a new transport for the broker code, accessible by specifying MSGFLO_BROKER=rabbitmqtt://.
The different participant should not need to care however, as they continue to use standard MQTT.
RabbitMQ supports MQTT, and can do routing of messages between different queues/exchanges, at least for AMQP (where we already use it). This is nice because MsgFlo can stay out of the direct message passing codepaths. If possible, it would be nice to use this also on MQTT.
However, since this is not a part of standard MQTT we likely need to keep our existing own routing code around as well. Probably this will be a new transport for the broker code, accessible by specifying MSGFLO_BROKER=
rabbitmqtt://.The different participant should not need to care however, as they continue to use standard MQTT.