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.

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

Feedback on message delivery #44

Open
zpostfacto opened this issue Jan 18, 2019 · 1 comment
Open

Feedback on message delivery #44

zpostfacto opened this issue Jan 18, 2019 · 1 comment
Assignees
@zpostfacto
Labels
enhancement New feature or request

Comments

@zpostfacto
Copy link
Contributor

We know which messages have been acked. Indeed, we have expended significant energy to do this efficiently. We should expose this information to the application, so that they won't re-implement this functionality themselves.
@zpostfacto zpostfacto self-assigned this Jan 18, 2019
@zpostfacto zpostfacto added the enhancement New feature or request label Jan 18, 2019
@nxrighthere
Copy link
Contributor

This feature would be very useful in state replication implementations with eventual consistency.

@nxrighthere nxrighthere mentioned this issue Feb 3, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zpostfacto zpostfacto

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zpostfacto @nxrighthere