call websocketDidConnect delegate after connected is set to prevent race condition #144
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
|
I think this will fix #147, correct? |
|
Ok cool. Thanks! |
daltoniam
added a commit
that referenced
this pull request
Dec 23, 2015
call websocketDidConnect delegate after connected is set to prevent race condition
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.
Attempting to write to the socket during websocketDidConnect fails silently sometimes because connected is not set until after processHTTP returns. The isConnected guard in dequeueWrite can execute before connected is set to true.
This change ensures that connected is set before calling the delegate.