Fix connect method not throwing on failure #49
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
Yoann-Abbes
reviewed
Apr 7, 2021
Yoann-Abbes
approved these changes
Apr 7, 2021
jenow
reviewed
Apr 7, 2021
jenow
approved these changes
Apr 7, 2021
added 2 commits
April 7, 2021 17:35
…leio/sdk-jvm into 48-fix-connect-not-throwing
Merged
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.
What does this PR do ?
This PR fixes the connect method of the WebSocket protocol by making it throw when the connection has failed.
Enhancements:
Avoid recursion in
tryToReconnectAvoid spawning N threads when trying to reconnect
Avoid triggering a
networkStateChangeCLOSEevent when the reconnection is successful