Thanks Christoph, I was about to talk about MQTT v5 activities.
As well as server/client development, we should take this
opportunity before the specification is finalized to feed back
suggestions to the OASIS Technical committee. The mailing list is
here:
https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=mqtt
There will be a 90 day period public review period soon, before
it is finalized, but the sooner any comments are made, the
better. Once the specification is finalized, we'll have to live
with the consequences for a long time!
James has completed a Java MQTT packet library, and aims to build
on that for a complete client. We took the view that a totally
new client was appropriate, given the differences in the
standards, and that the old client had so much historical
baggage. It does mean that an application would have to be coded
differently from V5 to V3, but the extra features in V5 are
substantial, so that writing common code for both V5 and V3 is
probably not worthwhile.
Ideally, I would like to get a V5 Paho (Python) test broker up
and running as soon as I can, but that will depend on my ability
to fit it in. (James has just offered to help me with that.)
Ian
On 01/20/2017 08:55 AM, Krey Christoph
wrote:
I think the community would benefit from an status update on
v5 implementation projects and interoperability testing
opportunities.
- I assume the v5 spec to be quite stable.
- I will start implementing client side v5 now and will use
any publically available broker for testing.
Cheers
Christoph
Von meinem iPhone gesendet
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
--
Ian Craggs
icraggs@xxxxxxxxxx IBM United Kingdom
Eclipse Paho Project Lead; Committer on Eclipse Mosquitto;
Tech Lead in IBM Watson IoT Platform