One of the weaknesseses of Message queueing protocols (MQP) is that it is a little different from HTTP.
The easiest/most usual or common type of service to validate for security is HTTP and validating any other protocol through vetting organizations can be a barrier. It can also mean bulkier mobile apps, having to support additional protocols.
seamless web messaging is a long time ask. the mosquitto mqtt broker now includes websockets, and so making Sarracenia speak to that as a client would be great.
it looks like one can just add an option "transport=websockets" on the existing mqtt client... so might not need a whole driver... just a way to express new url "mqttws" for web services...
One of the weaknesseses of Message queueing protocols (MQP) is that it is a little different from HTTP. The easiest/most usual or common type of service to validate for security is HTTP and validating any other protocol through vetting organizations can be a barrier. It can also mean bulkier mobile apps, having to support additional protocols.
seamless web messaging is a long time ask. the mosquitto mqtt broker now includes websockets, and so making Sarracenia speak to that as a client would be great.