-
1. Re: Cache structure - tree
marc.fleury Apr 17, 2003 5:37 PM (in response to belaban)hey, bela,
I am not totally sold on the tree structure (neither is bill). I mean if we AOP everything then tragging independent state changes is a trivial problem and we don't need individual entries in the cache structure. Can you explain why you decided to that again? -
2. Re: Cache structure - tree
belaban Apr 18, 2003 11:39 AM (in response to belaban)> hey, bela,
>
> I am not totally sold on the tree structure (neither
> is bill). I mean if we AOP everything then tragging
> independent state changes is a trivial problem and we
> don't need individual entries in the cache structure.
> Can you explain why you decided to that again?
I see that tree-structured cache as a valid building block in itself. 2 stages:
#1 Replicated cache
+ can be transient or replicated (async/sync)
+ optional acidity (locking, serializability etc)
- manual put() to track and replicate modifications
+ fast, efficient, no overhead (AOP)
#2 Replicated cache with AOP
+ acidity in interceptors
+ automagic tracking and replication of modifications
- more overhead, e.g. spiking of classes, 1 addtl object/POJO (in case of proxies, e.g. for collections)
I give people a choice of #1 or #2.
Also: I want to be able to provide #1 soon. #2 needs some more discussions with Bill.
Bela