Re: [paho-dev] Next Release of Paho after 1.0 (1.1?)

[Frank Pagliughi <fpagliughi@xxxxxxxxxxxxxx>]

Yes, 433871 was the big one that I was waiting on. It's the main thing I 
can't hide or figure out a work-around.

The other thing buried in that bug report is the request for a 
MQTTAsync_waitForCompletion() function. I was able to work around the 
lack of it inside the C++ wrapper but it took some code to do so, which 
I believed could be replaced by a single, small function in the C 
library. Let me know if I haven't convinced you yet!

Frank

On 06/12/2014 10:51 AM, Ian Craggs wrote:
> The actual release date for the C client (and the rest of Paho) is the 
> 25th June.
>
> I have the MQTT 3.1.1 updates ready in the development branch, and I 
> was hoping to get the long-awaited updates for the C++ compatibility 
> of the API into 1.0 as well 
> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=408283).
>
> I was also thinking of trying to fix 433871 (Outgoing messages should 
> be able to be tracked while they are queued up) for 1.0, but that will 
> probably have to wait, as I'm getting the Javascript and Java client 
> 3.1.1 updates ready.
>
> I don't think any of these changes should impact you too much, with 
> the possible exception of 433871.  In my mind, I've scheduled 1.1 for 
> August/September.
>
> Ian
>
>
> On 06/12/2014 03:01 PM, Frank Pagliughi wrote:
> > I have a number of updates for the C++ client that are nearly ready 
> > to go. If the C client is relatively stable at this point, I can 
> > start testing and get them uploaded in the next few weeks.
> >
> > Frank
> >
> > On 06/12/2014 06:13 AM, Ian Craggs wrote:
> > > Starting to think about the next release of Paho after 1.0, I've 
> > > created a release 1.1.
> > >
> > > Potential items to include:
> > >
> > > - the Android service
> > >
> > > - C++ client layer
> > >
> > > - embedded C/C++ clients
> > >
> > > - simple offline buffering for the Java, JavaScript, Python and C 
> > > clients.  This is something that we get asked about from time to 
> > > time.  The reason we haven't done it is because it does add 
> > > complications, in the management of the persistence store for 
> > > example.  It would (might?) be good to get a consistent approach 
> > > across the released clients.
> > >
> > > - MQTT 3.1.1 test material
> >
> > _______________________________________________
> > paho-dev mailing list
> > paho-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/paho-dev