Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] one mqtt-c client for publishing and subscribing

Hi Angelika,

It purely depends on the use case. If you are subscribing unnecessarily, you increase the network traffic. I am kinda doing the same and decided to have them separately.  Also, keep eyes on your stack. Many problems I have had are related to stack life.


On Wed, Mar 21, 2018 at 4:55 PM, Haenel, Angelika <angelika.haenel@xxxxxxxxxxxxxxxxx> wrote:

Hi all,


I plan to implement a flexible c++-Library for Publish-/Subscribe Pattern. The intention is to change the underlying message system without changing code.


Starting with some tests, I wonder if it would be a bad idea to use one mqtt-c client for publishing and subscribing at same time?

When I implement a test application with two modules A and B connected to mqtt, sending message from A to B and in the receiving routine of B sending back to A (and this very often), after a while I get corrupted output.

But when I use a different client for publishing everything works fine.


Any suggestions?





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

Back to the top