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

Support Version differences between the Client and Server #67

Closed
ghost opened this issue Apr 12, 2018 · 1 comment
Closed

Support Version differences between the Client and Server #67

ghost opened this issue Apr 12, 2018 · 1 comment

Comments

@ghost
Copy link

ghost commented Apr 12, 2018

How do you handle the situation where you have V1 Client and v 1.1 server ?

There are a few techniques which i wil raise for discussion as i have tried a few difference ones.

  1. Keep the URLs always the same and pass the version of the client in the header. The server then detects the version in the header and then handles the request this way. Not changing the URL is the whole point here as if you do then so much else has to constantly change.

  2. Use GRPC. GRPC was designed so that the client and server can use have Data type models that are different in that if a field is added to the server model the client does not freak out.

Maybe some others.... ?

@roughike
Copy link
Owner

Hi! I'm not sure if this is needed for this app. I don't really control the API, and it has stayed the same for years anyway. The API also doesn't support versioning.

I'll close this one for now and reopen if this ever becomes a problem.

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