On 2005-10-15, Barry Moore <[EMAIL PROTECTED]> wrote:
>
> This is the first thing that came to mind for my current needs. I have
> a database serving up data that is then computed and crunched in various
> CPU intensive ways before being sent to the browser. My database might
> only be updated once a month right now. I'd like to cache all those CPU
> intensive displays and then when I update the db, be able to globally
> clear all caches and start over. Haven't had time to think much about
> how to do that yet, but FWIW that's how I'd try to use something like
> Plugin::Cacheable.
I think this would be fairly common desire.
For this, I think you need to:
A. Recompute and cache when the data changes
B. When viewing, it always use the cache.
Or:
A. When viewing, always check if the cache is up to date.
B. If it's not update, update it.
C Display the cached version.
There is no correct expiration time to use with the standard cache
design, because you can't guess when the data will change next.
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
