-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add the version protocol header #19
Comments
We need to set up a policy regarding protocol versions to deal with this issue. For now, the following should be enough:
It means that 1.1 server should behave as 1.0 server to work with 1.0 client and vice versa. It can be achieved by exchanging each implementation's protocol version when handshaking. |
As for transport versioning, it will apply to only transports Cettia maintained, i.e. HTTP streaming and HTTP long polling except WebSocket. |
* A workaround for URI in WebSocket transport seems to conflict with the current version of `ws` package. Fixes #19
Now that the beta is over, it's time to version protocols, one for socket and one for each transport. Generally, version information is referenced in the handshaking so the protocol header would be proper.
cettia-version
w/ the initial value1.0
.cettia-transport-version
w/ the initial value1.0
.The text was updated successfully, but these errors were encountered: