For WAMP, Crossbar.io has a sophisticated meta API implemented - see here.
We should have something similar for clients connected via the MQTT.
Some of that functionality might already be there automatically, since the MQTT bridge will use the same internal ApplicationSession class in the routing core that WAMP-WebSocket clients use.
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/37996240-mqtt-router-meta-events-meta-procs-api?utm_campaign=plugin&utm_content=tracker%2F462544&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F462544&utm_medium=issues&utm_source=github).
For WAMP, Crossbar.io has a sophisticated meta API implemented - see here.
We should have something similar for clients connected via the MQTT.
Some of that functionality might already be there automatically, since the MQTT bridge will use the same internal ApplicationSession class in the routing core that WAMP-WebSocket clients use.