Sergio R. Caprile

> have You solved that issue? Nope, I've left the project aside until I either get support or have the extra time to play around with this. I'll post it...

I've had no problem using this library, which is also true for many other developers. What is your issue, _exactly_ ?

Yes, either both `MQTTPacket_decode()` and its child `MQTTPacket_decodenb()` (through the definition of `struct MQTTtransport`) assume `int` is at least 32-bits wide. In fact, now that you mention it, this assumption...

I guess you don't have 16K+ RAM available to hold 16K MQTT packets on your 16-bit device, so you most likely will need to discard these packets anyway. A packet...

According to RFC-2119, which MQTT3.1.1 cites as the definitions for its terminology usage, the word SHOULD means: "_SHOULD This word, or the adjective "RECOMMENDED", mean that there may exist valid...

Try to provide a description on why you are doing what you are doing. What you describe as "some linux platforms don't support char >= 128" is "some users don't...

Well, that is a too broad, misleading, and perhaps incorrect description. What I think I see (perhaps I'm not seeing what you see) is that in the event that not...

Perhaps the proper repo is [this one](https://github.com/eclipse/paho.mqtt.c) ? Explain what you are calling and how you are calling it.

You're at the wrong repo. There is no reference for 'async_client' at the embedded-c repo. The class definition for your init call seems to be [here](https://github.com/eclipse/paho.mqtt.cpp/blob/master/src/mqtt/async_client.h), so I bet the...

Oh, if you happen to know more than the developers then please do it right and send a pull request!