Eclipse Paho 1.2.0 (Neon)

Release Date
Deliverables
  1. Updated (bug-fixed) version of the existing client libraries; Java, Python, JavaScript, C, .Net, Android and Embedded C/C++.
  2. Automatic Reconnect & Offline Buffering functionality for the C, Java and Android Clients.
  3. WebSocket support for the Java and Python Clients.
  4. Formal release of the Go Client

Client Versions

Client
Version

Java
1.1.0

C
1.1.0

JavaScript
1.0.2

Go
1.0.0

Android
1.1.0

m2mqtt (.Net)
4.3.0

Embedded C/C++
1.0.1

Python
1.2

 



 

Compatibility

Each of the MQTT components supports the MQTT v3.1.1 standard version of the protocol (https://www.oasis-open.org/standards#mqttv3.1.1).  Some may also support the older 3.1 specification.

Client
MQTT v3.1.1
MQTT v3.1

Java
✔
✔

JavaScript
✔
✔

Python
✔
✔

C
✔
✔

Android
✔
✔

Go
✔
✔

.Net
✔
✔

Embedded C/C++
✔
✔

 

The MQTT-SN components implement version 1.2 of the MQTT-SN specification (http://mqtt.org/new/wp-content/uploads/2009/06/MQTT-SN_spec_v1.2.pdf).

Internationalization

The client libraries have a limited number of messages for debug information (trace) and errors (exceptions), intended for application developers, not end users.  There are no current plans for internationalization.

Target Environments

Existing Components

  • Java - JDK 1.4.2 and above
  • C - Linux, Windows and Mac OSX. Can also be called from C++
  • JavaScript - Standard Modern web browsers that support WebSokcets, Node.js is not supported.
  • Python - Python 2.7, 3 and above.
  • .Net (m2mqtt) - .Net and WinRt, including Windows Phone
  • Android - SDK 9 and Above
  • Embedded C/C++ - Microcontroller operating systems such as mbed, Arduino.

New Components

  • Go - Go Runtime, available on Windows, Mac OSX, Linux and FreeBSD
Themes

Automatic Reconnect

If the connection between the Paho Client and the MQTT server is lost, the developer currently has to manage the process of re-connecting to the server themselves. Now, the Java, Android and C clients are joining the Python client with the ability to automatically attempt to reconnect once the connection is lost.

Offline Buffering

In situations where the connection has been lost in the Java, Android and C clients, they are now able to continue accepting messages to be published and buffer them until the connection can be re-established. Once this happens the messages are then sent in the correct order to minimise data loss.
This release is part of Neon