DeWitt,
> > Have you though about making SharedMemoryCache flush to disk if it
> > becomes full but before it's time to expire the data?
>
> I've done a lot of thinking about a multi-layered cache
> implementation. The API would be the same, but it would be clever
> about using MemoryCache -> SharedMemoryCache -> FileCache to make read
> access to data super efficient, and only persist outward on writes.
Along the same lines, how about making SizeAwareMemoryCache as well so that
you can specify just how much data you want stored in the cache. I haven't
really thought about the implications of this but it seems to me that it
would be a useful extension. Memory's normally tighter than disk space. And
being in a mod_perl server environment where you have large chunks of memory
already used for the web server, it would be good to keep a handle on the
cache growing too large.
I suppose you get a similar effect from just keeping the timeout short but
I'm thinking of a scenario where it's valuable to keep the data for a very
long time, so long as I know that I'm not using all available memory in the
process.
Daniel.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Daniel Little Metrex Systems Consulting Inc. [EMAIL PROTECTED]
210-294 William Ave. Tel: (204) 940-4553
Winnipeg, MB., Cel: (204) 955-0300
Canada, R3B 0R1 Fax: (204) 487-6680
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
