[openstreetmap/openstreetmap-website] Make the enhanced changeset stats available via the API (Issue #6719)
Tom Hughes
notifications at github.com
Wed Feb 4 11:15:11 UTC 2026
tomhughes left a comment (openstreetmap/openstreetmap-website#6719)
> So it is plausible that this might have been implemented in C++ 10 years ago because, at the time, Ruby was not up to the task. Either in memory consumption, speed, or something along those lines. Can't tell for sure, but it's plausible.
That was the reason cgimap started (for the map call, hence the name) but it then moved on as more calls were added both for performance reasons and just to try and make it a complete API implementation, which I suspect was the case here.
> The former maintainer left the project about 8 years ago.
As it happens I saw said former maintainer last week, but I didn't know to ask him about this ;-)
> What do you think of making it so that `/changeset/{id}` is handled by the Rails app (as opposed to cgimap as current)?
Sounds fine to me - that call is metadata only so there's no performance concerns.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6719#issuecomment-3846832205
You are receiving this because you are subscribed to this thread.
Message ID: <openstreetmap/openstreetmap-website/issues/6719/3846832205 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20260204/1e2a63e5/attachment-0001.htm>
More information about the rails-dev
mailing list