With MQTT the setup/coordinator process is the one that binds queues/topics together, as the broker cannot provide this functionality. For showing whats-connected correctly in live mode we need to detect this.
There are two main approaches here:
- make Coordinator do all the setup, such that the same mqtt.Broker instance is used. Then we can just call
.listBindings and make it.
- make mqtt.Broker (or rather routing.BinderMixin) send all its routing changes to a dedicated topic like
/fbp/routing. It would also need to listen to changes to these, and 'listBindings' should return these. Would be useful also to introduce a bindings-changed event.
Coordinator/Runtime then need to subscribe to these changes and notify UI over the FBP runtime protocol.
With MQTT the setup/coordinator process is the one that binds queues/topics together, as the broker cannot provide this functionality. For showing whats-connected correctly in live mode we need to detect this.
There are two main approaches here:
.listBindingsand make it./fbp/routing. It would also need to listen to changes to these, and 'listBindings' should return these. Would be useful also to introduce abindings-changedevent.Coordinator/Runtime then need to subscribe to these changes and notify UI over the FBP runtime protocol.