MQTT – machine-to-machine connectivity protocol
1–10 of 20 posts
Re: MQTT – machine-to-machine connectivity protocol
#2It would be nice if the protocol allowed extension points in the SUBSCRIBE action. Right now it's not possible to use dynamic authorization delegation using signatures.
Re: MQTT – machine-to-machine connectivity protocol
#3I've found MQTT really useful in M2M/IoT situations, but I often found that I wanted to make use of existing HTTP based web solutions in combination with my MQTT networks.
As the first thing on my wishlist, I recently made a little python library [1] to aid people in pushing selected MQTT events to KeenIO[2]. It's mainly for development and testing, but I've found it pretty useful in my applications.
[1]: https://github.com/ZoetropeLabs/keenmqtt [2]: https://keen.io
Re: MQTT – machine-to-machine connectivity protocol
#4It's ok (I use it a bit at work), but from reading the specs it seems like AllJoyn is much more powerful (though I haven't used AllJoyn).
Also the QoS parameter means different things depending on which server you use.
Re: MQTT – machine-to-machine connectivity protocol
#5It would be nice if the protocol allowed extension points in the SUBSCRIBE action. Right now it's not possible to use dynamic authorization delegation using signatures.
This is a feature of a lot of open source MQTT brokers (Mosca, Mosquitto). We used Mosquitto for our app (http://www.clementine.io), and added dynamic auth for SUBSCRIBE and PUBLISH.
Re: MQTT – machine-to-machine connectivity protocol
#6I wonder how hard it is to just use AMQP in these scenarios
Re: MQTT – machine-to-machine connectivity protocol
#7We're using MQTT extensively at Karma [1] as the communication protocol between our LTE devices and our backend services. It has worked really well for us, and we're super happy that we chose for MQTT in favour of our previous HTTP/JSON stack.
We're about to release a very detailed blog post about our MQTT setup on our blog [2], describing why and how we implemented our own MQTT server and how we hooked that up to our Ruby backend services and Redis. The post should be live somewhere this week.
Re: MQTT – machine-to-machine connectivity protocol
#8MQTT works OK on Android via Paho library, but it seems that changes to upcoming "Android M" will reduce its usefulness.
In the scenario the phone would go to sleep, incoming data on a socket should wake it up - then you could grab a wakelock and do some work.
However with the new Doze mode(s) this no longer seems to be the case. Now the only way to wake the phone up externally now is with GCM.
Its too early to know for sure (more previews of M will be released) but I'm curious how this end.
Re: MQTT – machine-to-machine connectivity protocol
#9MQTT is really nice for generic pubsub, but from what I've seen doesn't handle RPC-style transactions at all.
It is very hard to have something like this without requiring a whole bunch of ephemeral topics or lots of message id tracking on the client and server:
server> set this value to Z.
device> oops, in your previous command, Z is invalid.
Re: MQTT – machine-to-machine connectivity protocol
#10I can't wait for http://www.matrix.org to mature. But this looks interesting.