Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] [iot-wg] Future Requirements and Releases of Paho



I agree 100%.  This is why we are going to ‘launch’ a Java stack at JavaOne. I also think we need to make sure we have a polygot stack for non-java developers.  A lot of IoT will be C/C++, _javascript_ and other languages.


My hope is that for the Mars release we have an IoT package that developers can download and documentation that helps them to get started.





From: iot-wg-bounces@xxxxxxxxxxx [mailto:iot-wg-bounces@xxxxxxxxxxx] On Behalf Of Dave Locke
Sent: August-28-14 6:59 AM
To: IoT Working Group mailing list
Cc: General development discussions for paho project
Subject: Re: [iot-wg] Future Requirements and Releases of Paho


apologies if this email arrives twice sent from a non-authorised email address the first time: 


+1   Moving forward so that there are a cohesive set of IoT projects under the auspices of Eclipse is important particularly for large scale adoption.  Each project on its own has strengths but greater value can be obtained by bringing them together.   Once obvious Java stack is  Concierge, Paho,  Kura and Moquette and then others like Smart Home can sit on top... . 


On 28 August 2014 11:14, Andy Piper <andypiperuk@xxxxxxxxx> wrote:

From an Eclipse IoT community perspective, I feel like we should pursue interoperability (as a minimum) specifically with Ponte, Kura, Concierge, Mosquitto and Moquette to ensure that Paho components are first-choice integrations for those projects. There may be others I am missing. We should probably review with those project teams to see whether they feel we need to add specific functionality.


We also should sort out ongoing releases now that we are in a more stable mode, e.g. get a 1.0.1+ release out to address the Gradle/Maven stuff that has come up since 1.0




On Thu, Aug 28, 2014 at 10:56 AM, Ian Craggs <icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello all,

I'm wondering what the future of Paho should look like.  From two points of view: functionality and participation in the wider Eclipse community.

The reason is that barring a few relatively minor enhancements (automatic reconnect, publishing when not connected, persistence), I don't see that the existing client libraries (Java, _javascript_, C, Python) need a lot of new work, and could stabilize within the near future.

There may be new components - client libraries in different languages, or a different style of library for a different purpose (like the embedded C/C++ APIs I'm working on at the moment).

So the first question:  are there Paho features, additional to the current libraries, or new components, that would be useful to the Eclipse IoT community?

The second question is about participation in Mars and future simultaneous releases.  If the Paho components were stable but still useful, how would Paho participate in a simultaneous release?

Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Committer on Paho, Mosquitto

iot-wg mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit



Andy Piper | Kingston upon Thames, London (UK)
blog:   |   skype: andypiperuk
twitter: @andypiper  |  images:

iot-wg mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit


Back to the top