QoS1 with no persistence and no retry: Like QoS1, Message delivery is acknowledged with PubAck, but unlike Qos1 messages, these are neither persisted and nor retried at send after single attempt. The message arrives at the receiver either once or not at all
QoS1 with no persistence and with retry: Like QoS1, Message delivery is acknowledged with PubAck, but unlike Qos1 messages, these are not persisted. The messages are retried within current session if delivery is not acknowledged
:warning: **
These are non standard QoS options. You need to have compatible broker to use these QoS options
When subscribing with special QoSes, byte flag(s) will be added to the payload
When publishing with special QoSes, QoS will be sent as 1 to the broker but with no persistence on client side.
We added two more Qos options:
QoS1 with no persistence and no retry: Like QoS1, Message delivery is acknowledged with PubAck, but unlike Qos1 messages, these are neither persisted and nor retried at send after single attempt. The message arrives at the receiver either once or not at all
QoS1 with no persistence and with retry: Like QoS1, Message delivery is acknowledged with PubAck, but unlike Qos1 messages, these are not persisted. The messages are retried within current session if delivery is not acknowledged
:warning: **
These are non standard QoS options. You need to have compatible broker to use these QoS options