Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] MQTT C++ Paho Client - Delivers QOS2 message before hand-shake is complete

Hi Rajesh,

The state it stores through the qos2 flow will ensure it does not deliver a duplicate message until the flow completes.

When it delivers the message on receipt of the publish, it must still store the ID of that message until the PUBREL/PUBCOMP exchange completes. That allows it to detect duplicate PUBLISHES arriving with the same ID.


On 11 March 2015 at 07:49, Rajesh Jangam <rajesh@xxxxxxxxxxx> wrote:

I have a small question regarding handling of QOS2 messages.
I noticed that in the C++ client, we seem to be delivering the QOS2 message immediately
after receiving the PUBLISH message from the broker.
We assume that the next sequence PUBREC/PUBREL/PUBCOMP is going to complete fine.
It may lead to re-deliveries by the broker (in case the next sequence does not finish up properly).

Please let me know your opinion.


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

Back to the top