[openstreetmap-website] way/:id/full/history (#130)

[Andy Allan]

This is the problem that Potlatch 2 faces for its history dialog, and indeed it fires off a bunch of node history requests to achieve the goal. Potlatch 1 has/had its own api as part of the AMF controller to acheive the result so didn't require N calls, but instead relied on the server doing more work.

In general expensive calls in the core API are avoided if there is a different approach that can be scaled decentrally - generally routes involving minutely replication and onto second-tier services like JXAPI. These history-of-way calls could be fulfilled using JXAPI (or whatever service is appropriate) but perhaps it's instructive that p2 queries the main API directly.

So rather than adding expensive non-critical calls to the core API, is there a mechanism to use decentralised services? What would be the current barriers against using decentralised responses? For a history call I don't think replication delay would be a problem, but I can see service reliability, and the lack of full-history-storing services being the main ones.

---
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/130#issuecomment-9363439
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20121011/2416aa35/attachment.html>