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

Jonathan Bennett notifications at github.com
Thu Oct 11 21:20:46 GMT 2012


I believe (based on a few minutes' reading) [entity tags](http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.11) (etags) perform exactly this function, so would be worth considering as a mechanism:

http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.11

The version number of an object would be used as the etag -- either verbatim or encoded somehow -- and returned with any request  Any downstream caches would be able to check the validity of their cached version by sending an if-none-match header to its upstream server. All responses in this system are cachable.


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


More information about the rails-dev mailing list