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

Manual acknowledgement #304

Closed
SgtSilvio opened this issue Jun 18, 2019 · 3 comments · Fixed by #403
Closed

Manual acknowledgement #304

SgtSilvio opened this issue Jun 18, 2019 · 3 comments · Fixed by #403
Assignees
Milestone

Comments

@SgtSilvio
Copy link
Member

No description provided.

@dowhiletrue
Copy link

According to #292 (comment) and #292 (comment) it is not possible to receive AND process a message at least once. Message may get lost, if the app terminates ungracefully right after a message is acknowledged, but not yet processed.

Therefore this feature or another mechanism, that ACKs a message after the callback is called would make sense for applications, that relay on guaranteed message processing.

So please, dear GitHub user vote for this feature!

@SgtSilvio SgtSilvio added this to the 1.2 milestone Nov 12, 2019
@SgtSilvio SgtSilvio self-assigned this Apr 6, 2020
@SgtSilvio SgtSilvio linked a pull request Apr 15, 2020 that will close this issue
@SgtSilvio
Copy link
Member Author

@dowhiletrue manual message acknowledgement is finally part of version 1.2.0, please check it out

@yilezhu
Copy link

yilezhu commented Jun 23, 2021

Is there any case of manual message acknowledgement by mqtt5client?

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

Successfully merging a pull request may close this issue.

3 participants