Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[paho-dev] Paho Website

Dear Paho community,

I have been using Java Paho for a while now quite successfully in an
Android application. Everything seems to work quite well, although I
wasn't even aware of the subproject
mentioned in a post last week (for my project, I have adapted to Paho). Thanks for your good and
free (as in freedom and beer) software!

I would like to share some impressions from a pure Paho *user's*
perspective with you:

 - It is a bit annoying, that the website
doesn't offer the direct download of Paho jar files. Everything is
there, but needs to be found (in this case, in
). A direct link to mqtt-client-0.4.0.jar,
mqtt-client-0.4.0-sources.jar and mqtt-client-0.4.0-javadoc.jar would
not hurt anyone and could improve the life of those not using Maven.
The "Download" link in the project wiki
(top right) 404s.

 - It is not really clear, what the current version of Paho Java is
(the commit message "Prepare for 0.4.0 release" does not really sound
final...). There are no release notes anywhere, no changelog (apart
from commit comments) and no current roadmap. seems to be terribly
outdated and in this case old information is maybe even worse than no
information at all (people might try to find the 0.9 version released
in 2Q13 or wonder, whether Kepler includes Paho or not,...). I figured
out from my own experience that, e.g., in 0.4.0 MemoryPersistence
moved from "internal" to "persist", and in messageArrived topics are
now Strings instead of MqttTopics and deliveryComplete expects
IMqttDeliveryToken instead of MqttDeliveryToken - but I am sure, much
more interesting things have changed and need to be considered.

It would be great if you could link more prominently to the JARs,
remove some old stuff from the wiki and put some blog-like information
on releases and current activities on the website. That would make
your project more accessible for novice users and would make the kind
of solid impression that users expect from infrastructure, they want
to build their applications on.

Best regards,


Back to the top