Transports order of preference #405
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
|
The handshake response shouldn't change based on the client transports preference. |
|
Sure. I think handshake return something like "supported transports". |
|
But you're saying the client is not generating the right intersection of transports. |
|
Sry for bad english. |
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.
When set list of transports as ['xhr-polling', 'jsonp-polling', 'websocket', 'flashsocket']
I wont try first connection to 'xhr-pooling', but connecting to 'websocket'
From server returned "16698093471053227150:60:256:websocket,flashsocket,xhr-polling,jsonp-polling" (websocket first)
I think after util.merge() list of transport be broken.
Small fix solve this problem