Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[paho-dev] Questions about Paho Release 1.1, Android Service and Embedded Client

Hello all,

as you probably know, I scheduled a release of Paho for the end of this month. The date is just one I made up, there's no particular dependency on that, so it could be changed. That's not true for 1.2 which is timed to coincide with the release of Eclipse Mars, that date is hard and fast.

The major items for inclusion in the 1.1 release are:

1) first formal release of Paolo's .Net (and WinRT!) client within Paho. No problem here :-)
2) Android service
3) embedded client

I did think about including the test material, but I really want to do more work on that first.

Two things are "worrying" me.

1) I've not yet been able to review the Android service at all. I really would like to before releasing it, but I haven't had the time. I'm just in the process of setting up Android Studio so I can try it out. Can anyone who has used it please give me their thoughts on:

a) how good it is
b) what areas that should be improved
c) and whether it is good for a 1.0 (production-ready) release? (Bearing in mind that strictly we can't change the API breaking backward compatibility once we get to 1.0, unless we move to a 2.0)

Any feedback would be most appreciated.

2) I really wanted to change the embedded API, MQTTClient, to use fixed width types (int8_t etc), so that we could be sure they would have a specific size on any hardware. I have had one bug (on Arduino) where the different size of an int was the cause. I could make that change before the Paho 1.1 release, but even if I did, I would like to make sure that the API did not need any other changes/fixes before going to a 1.0 (meaning stability) for the embedded client.

These concerns would be less important if we could release the Android service and embedded client at a sub 1.0 version number, say 0.8 or 0.9, because we could change the external APIs if we needed to, before we reached 1.0 for these components. That's what I'd like to do, but I don't know whether that would be acceptable as part of a Paho 1.1 (mature) release.

Again, all thoughts gladly accepted. If no one says I shouldn't, I'll go with the < 1.0 version numbers for the Android service and embedded client.

Thanks

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Paho Project Lead; Committer on Mosquitto



Back to the top