On 21 Jul 2004, at 10:35, Werner Guttmann wrote:
If you happen to have any questions, please bear in mind that I will not be
able to help you as I am away next week, and won#t be returning before
August 3rd, 2004.
Of course. :)
Well, not really ... as all I'll be doing is make Cache.java implement java.util.Map. As it stands right now, Cache.java does implememt some (actually most of) of the Map methods, but not all.
No problem, then.
Once I have done this, I'll need to update all current cache implementations
as well, adding default/dummy method implementations. Then, and only then,
I'll start to implememnt a distributed cache implementation.
What would be very nice, actually, is if you could support multiple caches. :) But that's a more difficult proposition, and I can always build a 'wrapper' cache that ties those multiple caches together in the way I'm looking for.
(try get on short-term memory; if not in short-term memory, locate in long-term memory and push into short-term memory. If not in long-term memory, fail. When set is called, update in both long-term and short-term memory. When delete is called, delete in both.)
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
