8000 Possibility of not acknowledging a published message · Issue #115 · wialon/gmqtt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Possibility of not acknowledging a published message #115

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.

Sign up for GitHub

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

Jump to bottom
Open
canique opened this issue Sep 2, 2020 · 1 comment
Open

Possibility of not acknowledging a published message #115

canique opened this issue Sep 2, 2020 · 1 comment

Comments

@canique
Copy link
canique commented Sep 2, 2020 •
edited
Loading

Based on #113 I suggest to have the ability to not acknowledge a message at all.
So it should be possible to "return None" in the on_message callback (without raising an exception).

Why? If I want to process a message, but some backend system that I need for processing is unavailable right now, I'd either have to store the message locally somewhere (and process it later) or let the broker know that I have not processed it at all.

Another partial solution would be to disconnect from the broker as long as the backend is unavailable, but still there is a time window where some messages might slip through.
@canique canique changed the title Possibility of now acknowledging a published message Possibility of not acknowledging a published message Sep 2, 2020
@Mixser
Copy link
Contributor
Mixser commented Sep 7, 2020

Hi, @canique

Good point, we will implement this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Mixser @canique
0