fix(WebSocket): buffer sending the data until connection is open #678
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.
When fixing the tests for our Socket.IO bunding, I've discovered that
client.send()
dispatches the message event on the WebSocket client immediately. If the client connection is stillCONNECTING
at the point, the message will be lost.Changes
client.send()
schedules data send for once the connection is open if it's not yet.client.send()
does nothing if the connection isCLOSING
orCLOSED
.