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

[mmd]

> If successful there is no need to update the local data after the fact, as that is only an optimisation (which iD for example does), which can be replaced by downloading again.

Well, this is how JOSM works today. All local placeholders get automatically updated by the diffResult, and re-downloading the area isn't really needed. In special cases where people use e.g. sparse editing, it might even be impossible to by simply re-download an area using the /map call. JOSM handles this case pretty well today solely based on diffResults.

> Chunked uploads are problematic, but that isn't covered by the original proposal either.

In my understanding of how JOSM works, chunked uploads are simply a series of changeset upload API calls,. The idea is that the editor temporarily assigns a unique identifier to each chunk before uploading. If there's some issue while uploading a chunk, a retry would simply provide the same id in the upload.




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