On Sat, Mar 10, 2001 at 11:17:21AM -0800, Bill Moseley wrote:
> When you say successor to File::Cache does that means File::Cache
> will not be maintained as a separate module anymore?
There are no features in File::Cache that will not exist in
Cache::FileCache and Cache::SizeAwareFileCache. Actually, as far as I
know, the only old feature missing at all from the new code is the
ability to tell the cache not to physically remove expired objects.
There is a backdoor around this in 0.03, however, so if you need that
functionality, it is already possible.
I'm hoping to retire File::Cache soon unless I get another maintainer.
But it seems silly to have redundant efforts. The new code is much,
much, better.
> 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.
I'll mark that down as a potential 0.04 feature. Thanks, Bill!
-DeWitt
