This is a bugfix release.
This is a bugfix release:
This is a bugfix release.
This is a fairly minor feature release. The major changes are the pattern matching ACL support, the support for running directly as a Windows service and the change to the network code to attempt to send packets immediately. The Windows binary is now supplied as an installer rather than a zip file.
max_connections to work again.will_set function.will_set functions for payload=None.clean_session=false set were
not being sent until the next message for that client was received. This has
been fixed (bug #890724).I've just added some more Linux repositories to the download page for Fedora 16 and SLE 10, 11 and 11 SP1.
Note that mosquitto-python isn't available on SLE 10.
See the download page.
To celebrate the news that the IBM Java MQTT client implementation will be released as open source, I've put together a simple Android example based on the MQTT service code written by Dale Lane. I'm a beginner at both Java and Android, so expect it to be a bit rough.
The example displays incoming payload text on a text label. It's a complete project that you can build and install on your phone with only a few small changes - search for "CHANGE ME" in src/org/mosquitto/android/mqtt/MQTTDemo.java.
To get the project working, assuming you've already installed the android sdk, first get the IBM Java library (see http://mqtt.org/software) and put it in <project dir>/lib then do the following:
android update project -p <path to project> # If the update complains about build.xml - delete it and run again cd <path to project> ant debug sudo adb start-server ant installd
I'll not be at all surprised if there are problems in the project due to different sdk or tool versions. Please comment if you find a problem.
The project is available from http://mosquitto.org/files/examples/android-mqtt-example.zip. Until the IBM Java implementation is open source please be aware of the licence attached to it.
Thanks to Dale for the core Android MQTT service implementation.
The web is currently buzzing with the announcement yesterday that IBM and Eurotech are donating MQTT to the Eclipse Foundation. One part of this is the new Machine to Machine Working Group, again part of Eclipse. Another much more significant part has been released as part of a new Eclipse open source project Paho, which is in the proposal stage.
The exciting part is the "Initial contributions" section which states "The initial code contribution to Paho will include Java and C client-side implementations the MQTT protocol, contributed by IBM. "
It looks like the code will be licensed under the EPL (Eclipse Public License). This is particularly exciting because there is currently no solid freely available and usable implementation of MQTT in Java.
Well done everyone at IBM for making this happen. Roll on the end of November!
Update:
This post on mqtt.org explains what the various announcements mean more clearly: http://mqtt.org/2011/11/eclipse-paho-open-source-and-other-news
Update 2:
Andy Piper's blog post covers things even better, along with clearing up some of the confusions from the news releases: http://andypiper.co.uk/2011/11/04/mqtt-goes-free-a-personal-qa/
Today (just) marks the 2nd birthday of the mosquitto project. In the past year mosquitto has undergone pretty substantial changes and improvements. Some highlights from the year:
Mosquitto has gone from version 0.8.3 to 0.13 - so what about next year? This will be the year when 1.0 is released. The bar I'm setting is complete RSMB features, with the exception of some of the more esoteric ones. At the moment this means there are still some of the bridge features to implement and complete configuration reloading. I'm also going to have a much improved Windows port so there will be no need for a separate Cygwin version. At the same time I'm making a Windows installer and allowing mosquitto to be installed as a proper Windows service. This work should all be in 0.14. Another point for improvement is the Python module - it could be more Pythonic than it is now. My current plan is to have it throw exceptions rather than return integer error values but I could do with the help of a Python expert really.
All in all I think it should be a good year.
Stephen Nicholas has carried out some power usage analysis of MQTT on Android. Details are at http://stephendnicholas.com/archives/219 and the conclusion is that it doesn't use much power.
This release brings some new features and fixes. Although there are no real "killer features", this release does include some fairly significant updates. Of particular note are the fixes to subscription wildcard matching, which now meets the spec in all cases, the Python payload parameter being a Python string which should make life lots easier for Python developers, the non clean-session client fixes and related persistent database fixes.
max_queued_messages
option is now obeyed.