On Thursday 06 December 2001 21:57, Sebastian Rahtz wrote: > Would people like to outline their AxKit cache-housekeeping > mechanisms? We started off with a simple reaper which > zapped files which had not been accessed for a week, but this > seems to break AxKit. I assume this is because a call for foo.bar.baz > generates XXXX and XXXX.gz, which may get accessed at different times. > But then AxKit seems to assume XXXX.gz exists if XXXX does. > > I assume that a) people *are* using caches, and b) are not > simply flushing them by hand?
Yes, we're using cache here, but we don't do housekeeping. Very rarely, when I need to clean it I just erase it entirely. Granted, this may not be the best approach, but so far I haven't seen the need for good housekeeping there, though the amount of cached files is large. I know I'll need it at some point, and that the multi-level caches won't help (because it doesn't delete cache for deleted docs). Imho the best way would be to have this functionality built into AxKit's cache API. The reason for this is because Cache is pluggable, and one may want to do cleanup irrespective of the cache module used. If anyone feels like becoming one of the oft-sang 1.5 heros.... :-) -- _______________________________________________________________________ Robin Berjon <[EMAIL PROTECTED]> -- CTO k n o w s c a p e : // venture knowledge agency www.knowscape.com ----------------------------------------------------------------------- Suicidal twin kills sister by mistake! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
