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

Mateusz Konieczny notifications at github.com
Sat Apr 20 11:10:57 UTC 2019

> one app misbehaving. solution: tell them to stop and document why auto retrying is a bad idea

So what JOSM should do? I would be happy to open issue on their bug tracker but based on https://github.com/openstreetmap/openstreetmap-website/issues/2201#issuecomment-480503602 I see following solutions

- reupload, currently used by JOSM (leading to potential duplicates)
- refreshing the data in the editor - while it may be feasible in iD it is probably not doable in JOSM. Note that JOSM allows to load data for massive area, not resonable to reload. And it may be loaded for example from overpass queries (one may easily have 10 000 objects scattered across world, refreshing areas by downloading data for such area is not going to work and rerunning queries is going to fail as soon as overpass has lag greater than measured in seconds.
- replace the data in the editor - potentially losing all edits by user is worse than occasional duplicates that are fairly easy to handle. It also runs in all problems of a previous solution.

Maybe I am missing something but I see no way to improve things on a JOSM side.

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...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20190420/2ded1438/attachment.html>

More information about the rails-dev mailing list