[openstreetmap-website] Increase cachablility for individual OSM elements on the API (#129)

apmon notifications at github.com
Fri Oct 12 00:52:11 GMT 2012

Although it probably is fairly easy to implement, i.e. you probably only need a single line of ruby to not set private HTTP headers, (at least for the already versioned calls) I am not sure in which scenario you would see a reasonably high enough hit rate to make any difference on either server side load or client side latency. Can you give a typical use case?

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/20121011/15058c61/attachment.html>

More information about the rails-dev mailing list