Add an initialPacket option
#471
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
This was referenced Jan 18, 2017
|
Question: Should it rather be an async callback? I was thinking to use it that way in Socket.IO:
|
darrachequesne
changed the title
additionalHandshakePacket optioninitialMessage option
darrachequesne
changed the title
initialMessage optioninitialPacket option
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 kind of change this PR does introduce
New behaviour
This PR adds a new option,
initialMessage, which allow to provide a packet that will be concatenated with the handshake packet. That will allow to merge Engine.IO (sent here) and Socket.IO (sent here) handshakes, in order to reduce the number of roundtrips necessary to establish a connection.Reviews are welcome! (and if you have a better name for the option...)