#1 Cache is not serializable. Memory usage limit.

[Anonymous]

Hello ,

I tried the shiftone cache. It is great. It has most of the
features I am looking for.

There are still two features I am looking for but it is not
supported yet.

1) I want to serialize the cache to disk.
As my standalone application will loop 5 thousands files
(10k – 400k). I may need to run the application several
times a day with different parameters. The files only
change once a day. It will take about 40 minutes to
loop these files the first time. If I store them in a
hashmap and save it to disk, it will only take 1 min to
load. So I hope the cache (and everything referenced
by cache) be serializable.

2) size limit.
Number of objects to be cache can be configured by
shiftone, but, if the size of each object is too different,it
is not useful to me. I am not very concern how many
entries the cache has, I only care how much memory
the cache occupied, say, 400 MB. Can this feature be
added next time?

Thank you very much for your excellent work.

Have a great day.

Steven

Email: steven_wysdom@yahoo.com

[Nobody/Anonymous]

Logged In: NO

Hey Steven,
(1) lets say I make it possible to save a cache to disk. How
would by cache behave differently from a
hashmap/hashtable? I would think expiration would be very
different.

(2) this can be done in a few ways, but I think most likely I
would implement it as a wrapper cache that would route
objects to one of several delegate caches based on size.
Each delegate cache could have different max sizes (#
objects) and expiration.

Thoughts?