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

Bryan Housel notifications at github.com
Sat Apr 6 15:52:30 UTC 2019


> I have to say that I don't find any of the 3 options you mentioned compelling, and that's the main motivation for opening up this issue. JOSM implements option 1, iD either 1 and/or 3 (not exactly sure at the moment), maybe some other editor does 2 already.

iD does option 3 currently "replace the data in the editor - potentially zapping all the edits by the user"

The reason for this is:  A thing we've seen users do which was surprising to me (but not really) is that users sometimes start their upload and then just close their browser tab and open a new one.  Obviously in situations like this, iD has no way of knowing whether that upload will ever complete, and offering to "restore" their changes will introduce duplicates, so we just wipe their history as soon as the changeset is inflight.

-- 
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-480514779
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190406/5210e885/attachment-0001.html>


More information about the rails-dev mailing list