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

[mmd]

At least for the changeset upload, I had the following design goals in mind:

* We store at most one I-Key per changeset
* One entry would have at most 800k in size for the payload (for a 10k changeset)
* Explicitly closing the changeset removes the I-Key
* Remaining I-Keys can be deleted after 1 hour, by the time the changeset automatically closes

I'd like to understand a bit better, what your design goals would be, and where exactly you see the issues. Is it in the number of messages, the size, something else? I'm not saying that we need to use a database for this purpose, just like to understand your concerns.

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