Justus Pendleton <[EMAIL PROTECTED]> writes: > On 2005-12-04, Piers Cawley <[EMAIL PROTECTED]> wrote: >> So, I'm about to start to add better tracking of cached pages, and I >> want to make sure that I've got my flushing rules straight in my head, >> so I'm brain dumping here. Here's the rules I've worked out so far: >> >> An article is created Uncategorized index pages > > Everything also has a "and maybe flush all pages depending on what > sidebars do" requirement. For instance, I have a sidebar that lists the > 5 most recent posts. So I need to flush the cache on every article > creation. It sounds like what you need is some way for sidebars to > register which actions trigger an update/flush for them.
Nice idea. The sidebar you're talking about would work fine with a 'nuke everything on article creation' approach, but that's not going to be the case for all such sidebars (5 most 'active' posts for instance). Personally, I become more and more convinced that we need to have some way of doing ajax rendering of sidebars. Or fragment caching, which brings its own set of problems because you have to track fragment dependencies. -- Piers Cawley <[EMAIL PROTECTED]> http://www.bofh.org.uk/ _______________________________________________ Typo-list mailing list [EMAIL PROTECTED] http://rubyforge.org/mailman/listinfo/typo-list
