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

Tom Hughes notifications at github.com
Thu Apr 18 09:25:43 UTC 2019


Sorry, I just find it really hard to express how weird this whole thing seems to me.

Maybe it's just me but ut really has the feel of a duct-tape-and-baling-wire solution - it's one of things where it's hard to explain but it's one of things where my engineer sense just kind of goes "urgh" on me. What is sometimes called a "code smell" or what I often like to think of as code aesthetics where something just feels wrong and you know deep down that there has to be a better way.

I think I've been clear from the start that I think the asynchronous API is the correct solution, though to be fair that is also going to need to store queued requests and responses somehow and I don't really have a clear picture of how that would work.

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


More information about the rails-dev mailing list