Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why not temporary store message for QOS1 and QOS2? #44

Open
zhaojh329 opened this issue Mar 13, 2023 · 4 comments
Open

Why not temporary store message for QOS1 and QOS2? #44

zhaojh329 opened this issue Mar 13, 2023 · 4 comments

Comments

@zhaojh329
Copy link

No description provided.

@Tieske
Copy link
Contributor

Tieske commented Mar 14, 2023

Can you clarify what problem you have that would be solved by this?

@xHasKx
Copy link
Owner

xHasKx commented Mar 14, 2023

I suppose you want QoS>0 messages to be reliable preserved until delivery confirmation.
If you really need that, you have to setup it somehow in your code independently of that lib, because it provides MQTT transport features only, without any kind of session storage.

@zhaojh329
Copy link
Author

Is message retransmission required for QOS1 and QOS2 in mqtt client?

@Tieske
Copy link
Contributor

Tieske commented Apr 15, 2024

Is message retransmission required for QOS1 and QOS2 in mqtt client?

The library doesn't automatically do this. So if you need this to be reliable, your application code should keep track of messages until confirmation has been received (and do retransmissions where necessary).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants