Hi Roger,
yes, it is compliant. QoS 1 and 2 will still work if you only retry
on reconnect, and that is the only requirement for retries to be
compliant with 3.1.1.
And I just noticed that the spec also notes:
Non normative comment
Historically retransmission of Control Packets was required to
overcome data
loss on some older TCP networks. This might remain a concern where
MQTT
3.1.1 implementations are to be deployed in such environments.
I think I removed the retries (except for connection
reestablishment) for the C client for MQTT 3.1.1. ... or did I?
I'll have to check that one.
Ian
On 05/20/2015 03:31 PM, Roger Light
wrote:
Hi Ian,
I can't help thinking that would remove the point of
QoS>0 :) Section 3.3.1 talks about retrying publishes.
Section 4.4 also discusses retrying delivery and states
that reconnecting with clean session set to 0 is the only
scenario when a client or server is required to redeliver
messages.
In conclusion I'm pretty certain that it is compliant.
Cheers,
Roger
_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/paho-dev
--
Ian Craggs
icraggs@xxxxxxxxxx IBM United Kingdom
Paho Project Lead; Committer on Mosquitto
|