Unset client ID when stopped #80
Merged
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
When the client invokes `stop`, it is signalling an explicit intent to disconnect. Therefore, subsequent connections should not be considered 'resume' events, but complete 'begin' events in their own right. By unsetting the client ID, multiple `run` invocations each behave identically (each sending a new 'begin' event to the server), and the 'resume' event is reserved for only unexpected re-connections.
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.
The current behavior is causing an error in my application because we are also using the "resource" conviguration for Socket.io to differentiate connections. When the user switches between connections, the "resume" event triggered by the server is labeled as "invalid".