[openstreetmap/openstreetmap-website] Capabilities call and versioning (#2162)

[mmd]

> Thinking about this some more I believe the theory was that is was unlikely the server would ever support more than one version at once but that clients might

Somehow this made me worry a bit, as it effectively means that we would have to cut off all old clients not supporting the latest and greatest version at a fixed point in time. Every version change will be a bing bang in the future.

Also, every editing app would have to incorporate code for the new version months ahead of time to be prepared. Then there's the user's update discipline that might further complicate things. 

My gut feeling is that this might be extremely difficult to get right, but I'm happy if you can prove me wrong.

Today, we have so many different API endpoints under the umbrella of the API 0.6 that don't really belong there. Examples could be changeset discussions, gps traces, user data, and probably also map notes. Any incompatible changes here don't really warrant a new OSM API version in a strict sense IMHO, and this further complicates overall API evolution. Maybe that's worth exploring in another issue.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/2162#issuecomment-470207138
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190306/d3367626/attachment.html>