On Mon, 27 Sep 2004 18:20:48 +0100, Matt Clark <matt@ymogen.net> wrote:
> This is very true. Client side caching is an enormous win for apps, but it
> requires quite a lot of logic, triggers to update last-modified fields on
> relevant tables, etc etc. Moving some of this logic to the DB would perhaps
> not usually be quite as efficient as a bespoke client caching solution, but
> it will above all be a lot easier for the application developer!
In the world of PHP it is trivial thanks to PEAR's Cache_Lite. The
project lead for Mambo implemented page-level caching in a day, and
had all the triggers for clearing the cache included in the content
management interface - not difficult at all.
Basically you set a default in seconds for the HTML results to be
cached, and then have triggers set that force the cache to regenerate
(whenever CRUD happens to the content, for example).
Can't speak for Perl/Python/Ruby/.Net/Java, but Cache_Lite sure made a
believer out of me!
-- Mitch
