3 ms·
Yeah I don't mean due to the protocol, I mean due to application bugs where something adds a message to some queue and the thing that is meant to process it doe
by IshKebab 5y ago
Yeah I don't mean due to the protocol, I mean due to application bugs where something adds a message to some queue and the thing that is meant to process it doesn't for some reason, and then nothing will ever realise.
Compared to callbacks / RPC for example, where you have a function call the either has to succeed or it has to fail.
It's not a deal breaker but I don't like it.
- RedShift1 5y agoIf your MQTT client allows control over this aspect of the protocol, you can just not ACK QOS > 0 messages that failed to process. Next time you connect you'll get the non-ACK'ed messages first.