Preliminary work to allow server to support multiple protocol versions #2017

Closed
NTaylorMullen opened this Issue May 13, 2013 · 3 comments

Comments

Projects
None yet
3 participants
Contributor

NTaylorMullen commented May 13, 2013

Essentially new clients will now pass their expected protocol version via the Query String to the server. If the server does not get a version number it will default to 1.2. Otherwise it will return 1.3. This way the client will be able to determine if it supports a valid protocol version.

@ghost ghost assigned NTaylorMullen May 13, 2013

NTaylorMullen added a commit that referenced this issue May 14, 2013

Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017

NTaylorMullen added a commit that referenced this issue May 14, 2013

Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 14, 2013

Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 14, 2013

Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017

NTaylorMullen added a commit that referenced this issue May 15, 2013

Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017

NTaylorMullen added a commit that referenced this issue May 15, 2013

Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 15, 2013

Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 15, 2013

Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017

NTaylorMullen added a commit that referenced this issue May 16, 2013

Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017

NTaylorMullen added a commit that referenced this issue May 16, 2013

Updated protocol in JS client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 16, 2013

Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 16, 2013

Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017

NTaylorMullen added a commit that referenced this issue May 17, 2013

Finished server side changes for protocol resolution
- Supports ranges for server protocols
- Also allows replacement of protocol resolver

#2017

NTaylorMullen added a commit that referenced this issue May 17, 2013

Updated protocol in C# client
- Also added the feature to pass the clientProtocol in the negotiation request

#2017

NTaylorMullen added a commit that referenced this issue May 17, 2013

Added tests to verify protocol handling on the server
- Includes JS, C# Client, and Server
- Had to add a little bit of extensibility to the test utilities for JS to allow overriding of the WrapConnectionStart functionality

#2017
Owner

davidfowl commented May 17, 2013

@NTaylorMullen isn't this done?

@ghost ghost assigned Xiaohongt May 17, 2013

Contributor

NTaylorMullen commented May 17, 2013

Just marked it correctly

Contributor

Xiaohongt commented May 18, 2013

verified without querystring and with querystring for different values

@Xiaohongt Xiaohongt closed this May 18, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment