On Wed, Apr 28, 2010 at 5:23 PM, Felix Meschberger <fmesc...@gmail.com> wrote: > Hi, > > Wow ! > > I didn't expect to have this discussion get in this direction, but excellent ! > > For illustration what I originally had in mind, I have commited my > prototype in [1]. > > Please note, that this *only* is about setting the Last-Modified and > Cache-Control headers. > > Now, taken a step further: do we really want to build a cache into > Sling ? Shouldn't we rather rely on some existing caching proxy for > this, like Squid or mod_cache/mod_proxy ?
Again from our project, we use Varnish [1] in front of our Sling app, and then remove objects from Varnish when there's a resource change event in Sling. Caching HTTP proxies are highly optimized to do just that, and trying to implement a good enough system in Sling seems to be duplicating work. What *would* be useful, is more low-level caching. Without having investigated any such possibilities, I can think of resource resolution, script results, access control ... [1] http://varnish-cache.org/ -- Vidar S. Ramdal <vi...@idium.no> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 21 531941, ext 2070
