Skip to content
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

Deal with client and server using different API versions #16

Open
armsnyder opened this issue Nov 30, 2020 · 0 comments
Open

Deal with client and server using different API versions #16

armsnyder opened this issue Nov 30, 2020 · 0 comments

Comments

@armsnyder
Copy link
Owner

Find some way to deal with the client being out of date from the server. The client sends its version number to the server on "hello" action already. Maybe the server can send back an "updateRequired" action if the client is old? What about when/if there are different types of clients like mobile or web? All that really matters is the version of the messaging API that the client is using. Should we version the API separately from the client? What should the versioning scheme be? Should the server support multiple API versions simultaneously? What do websocket API versions even look like?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant