4 ms·
> events can get lost, Well, yes, but QoS=1 or 2 with a reasonably large queue I haven't seen loss issues. What kind of loss problems are you running into (th
by SavantIdiot 5y ago
> events can get lost,
Well, yes, but QoS=1 or 2 with a reasonably large queue I haven't seen loss issues.
What kind of loss problems are you running into (that I should be worried about)?
- IshKebab 5y agoYeah 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.