Mosquitto client library vs eclipse paho

I am just looking into the details of Eclipse PAHO and Mosquitto client libraries (MQTT C ++ libraries). It looks like PAHO uses the mosquitto MQTT broker, but provides its own MQTT client libraries.

The Mosquitto library also provides a way to implement client libraries for the Mosquitto MQTT broker.

I would like to understand what is the main difference between these two client libraries. Discussed here , but it doesn't answer my question. Which is preferred over the other and why? and why does eclipse support both?

+3


source to share


2 answers


I faced the same problem: choose paho or Mosquitto C ++ client library for embedded Linux device. I tried a minimal app with PAHO first. It basically supports all the features I need, but the cpp library wrapper doesn't work and I feel like the main branch of the paho.mqtt.cpp project is not very well supported. Since there are two functions

  • encryption

  • set all connection parameters like mqtt version etc.


which are not offered via mainbranch cpp-lib in PAHO, I am going to use libmosquitto

with

+1


source


We used Paho C library and Java library. If you look at Paho C code, the quality of the code is poor. There was a problem in Java library where Linux deletes temp file and Paho doesn't recover - don't know if this affects version C. Trying libmosquitto for next project.



+1


source







All Articles