Functionalities for publishAsync while disconnected #229
Conversation
This file contains hidden or 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
Release of version 1.4.8
…t triggered + the id when performing publishAsync when disconnected returns 'queued' instead an id for track the callback
|
Greetings! Sorry to say but this is a very old issue that is probably not getting as much attention as it deservers. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to open a new one. |
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.
Before if a publishAsync was performed while disconnected the message was queued and the function returned 'queued' instead of a message id, also when reconnected the draining process send the messages in the queue but did not fire the callback
*Issue #226 and #196
Description of changes:
Now when a publishAsync is performed while disconnected a negative id is given, for tracking purposes with the callback and also for know that it's been queued (negative number = message queued). When reconnected, in the draining process, the specifyed callback is called with the (negative) id returned with publishAsync for tracking.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.