On 31 May 2011 10:34, Per Buer <[email protected]> wrote: > Hi > > On Tue, May 31, 2011 at 12:23 AM, Lukas Kahwe Smith > <[email protected]>wrote: > >> Hi, >> >> I assume some of you have stumbled over LCI by now: >> http://www.ietf.org/id/draft-nottingham-linked-cache-inv-00.txt >> >> This is actually quite interesting. For an application we are building we >> are looking to create an invalidation service to which the various >> independent frontend server applications can register and which gets >> notified by the backend. Of course the frontends then have to figure out >> which pages all need to be invalidated. The original article will be easy. >> Some of the category overviews will also be easy to delete. What will >> already get harder is invalidating all articles that reference the given >> article and worse yet would be if we start caching search results. >> >> So I am wondering if you guys are looking at LCI for a future varnish >> impovement and if someone has build something like this on top of varnish >> today already that could maybe help us here. >> > > I'm pretty sure this can be implemented in VCL. No need to place it on the > radar. I have an upcoming blog-post describing something similar. It might > get a bit hairy with all the regular expression so it might be cleaner in a > module. >
I experimented with something that sounds similar. Each page set a header recording the the content item ids that were used in rendering the page. They could then be purged with a regex including any dependents id. http://dev.plone.org/collective/browser/experimental.depends/trunk/varnish.vcl It works when you update or delete a content item, but it can't help the case where you add a new content item and want that to appear in listing. Laurence
_______________________________________________ varnish-misc mailing list [email protected] http://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
