Implement session state (full QOS1/2 support) and publish queue #172
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds support for Session State which enables full QOS1/2 support (with information about messages that are not completely acknowledged being stored in memory or on disk). Adding this functionality required major changes to the library, but most users' code should run without alteration (see the updated readme for further info). I have tested this code, but there will be bugs (and a few todos remain). I feel that it is good enough to be pulled into @master so others can test (and provide fixes).
|
Thanks for working on this @MattBrittan a big improvement that takes us that much closer to a v1 release |
This was referenced Oct 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds support for Session State which enables full QOS1/2 support (with information about messages that are not completely acknowledged being stored in memory or on disk). Adding this functionality required major changes to the library, but most users' code should run without alteration (see the updated readme for further info).
I have tested this code, but there will be bugs (and a few todos remain). I feel that it is good enough to be pulled into @master so others can test (and provide fixes).
closes #25