Thanks - yes, TCP/IP basically guarantees that all packets arrive, in the right order, and only once - so MQTT QoS is basically just reimplementing what TCP/IP does already.
Yes, there would have to be another connect packet if the connection was lost, but my point is that you might be using MQTT over WebSockets (for instance... or something else) in which case the reconnection code would be totally different.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thanks - yes, TCP/IP basically guarantees that all packets arrive, in the right order, and only once - so MQTT QoS is basically just reimplementing what TCP/IP does already.
Yes, there would have to be another connect packet if the connection was lost, but my point is that you might be using MQTT over WebSockets (for instance... or something else) in which case the reconnection code would be totally different.