Puback is ignored

[emitter-io]

Puback is ignored

[kelindar]

Currently, we only support QoS 0 (at most once delivery), hence the ignore of puback. We're going to add support for QoS 1 (at least once) going forward, and we will integrate our message storage with it as well.

[poonai]

@kelindar I would really like to work on this. retry based on puback is enough? I have one more doubt that if the network goes down socket will be lost right? In that scenario, how to do the retry. (I may be wrong). I already made some work in my local repo. If you can clear the doubt, I can send PR straight away now 😄

[kelindar]

@Sch00lb0y just seeing this. Would be great if you could help, feel free to send a PR so we can look. Some basic retry mechanism on PUBACK is a good start indeed.

The real question is when to send a PUBACK from the broker to the client, I'm thinking that we need to only send acknowledgement when the message is pushed for delivery within a cluster to the subscribers. This may require acknowledgements on gossip unicast level.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.