[openstreetmap/openstreetmap-website] Supporting multiple API versions (#2353)
notifications at github.com
Wed Oct 30 13:20:10 UTC 2019
> IMHO if you start considering stuff outside of just the core OSM data and API it becomes tricky
Unfortunately that's what I have to do - everything under `/api/` is affected by these discussions.
What do you consider as the limits of "core OSM data"? I assume at least nodes, ways, relations, and the output of the map call (e.g. the <bounds> element). Would you also include the users and changesets output? Both are referenced from a map response but only by id.
> carving up the API so that essentially independent parts can actually be run independent of each other
I haven't seen much discussion of that, if any. I know there were discussions in the past about running all of `/api/` separately from other non-api stuff, but not about splitting the api itself into multiple projects. But in any case, I've already been told off in this thread for referencing things that happened a while ago, so I won't delve too deeply into historical discussions.
I don't think it would solve any of the problem at hand though. If we split the API up into multiple software projects, it could still be run transparently at `/api/...` with an apache redirects config file. But then we'll still have all the same discussions about which number to put inside of which responses.
> In any case if we really want to indulge in 2nd system syndrome
Since I think given that splitting things up doesn't solve the topic of what numbers to put in the responses, I'm going to avoid this "2nd system syndrome" and declare it out of scope for this PR.
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rails-dev