[openstreetmap/openstreetmap-website] Idempotency for API 0.6 (#2201)

mmd notifications at github.com
Thu Apr 18 06:12:36 UTC 2019


By the way, I added a [working prototype](https://github.com/mmd-osm/openstreetmap-cgimap/commit/08a7b4831618494e3ff1cf9b77875fe9614672cc) to cgimap's changeset upload now, which we could use for further discussion, or maybe even deploy to the dev instance once we have found a good data model for the persistence layer.

I think that it makes sense to consider all parts of the API where we have some potential issues with idempotency, but I'd like to see a bit of a prioritization, to have a bit more of a focused effort.

As an example, I'd like to exclude "PUT /api/0.6/[node|way|relation]/create" in the first step, as it doesn't follow idempotency semantics anyway, although it is using the "PUT" verb, it's somewhat rarely used these days (none of the major editors use it), and remaining tools good easily just switch to the diff upload.

I think, besides changeset upload, we should only include [POSTing Notes](https://wiki.openstreetmap.org/wiki/API_v0.6#Create_a_new_note:_Create:_POST_.2Fapi.2F0.6.2Fnotes) as the second API call in a first iteration, and see how far we can get and work on any issues. Only once this is stable and all issues ruled out, extend the concept to the remaining bits of the API.


-- 
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/2201#issuecomment-484369680
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190417/6e601218/attachment.html>


More information about the rails-dev mailing list