Show HN: First ever MQTT and XMPP dual-protocol server
blog.process-one.net
blog.process-one.net
I'm not aware of anyone using it in production, or asking to - so it's not received a lot of attention. For my own projects I've tended to prefer bridging to XMPP in other ways, but it was fun to work on.
I found a number of things surprising in MQTT, for example the lack of errors in response to commands (such as publishing), with the only solution to be just closing the connection entirely.
I think the surprising behaviours of MQTT are its strength - it's minimal and perfect for low-energy devices. For heavy lifting, there's XMPP.
Our internal XMPP pubsub (XEP-0060) support has a native code API designed for use by internal modules, so there is no need to marshal everything from MQTT into the appropriate XMPP stanzas for example, it's a direct mapping from MQTT to our internal API.