Ard Schrijvers escribió:
/snip
If there are better alternatives to ehcache we should
consider them of
course. Personally I would like that this work will be
done in trunk
only. We could build an own maven project for each cache
implementation
which will reduce the
This is a partial fix of a larger problem that I am not yet capable of fixing:
removing cachekeys according the correct eviction policy.
This fix at least fixes the flaw, that the StoreJanitor could delete the entire
memoryStore part from ehcache. In the JCSDefaultStore, this size() method was
Thanks Ard. I will apply this patch today after work. :-)
Best Regards,
Antonio Gallardo
Ard Schrijvers escribió:
This is a partial fix of a larger problem that I am not yet capable of fixing: removing cachekeys according the correct eviction policy.
This fix at least fixes the flaw, that
Ard Schrijvers escribió:
Thx!!
You do not happen to know where the JCSDefaultStore went in trunk..?? I read
some stuff about it outperforming ehcache in almost every way (and that it
might be easier to implement the eviction policy driven freeing of cachekeys).
WARINIG: I am far to be a
You do not happen to know where the JCSDefaultStore went in
trunk..?? I read some stuff about it outperforming ehcache in
almost every way (and that it might be easier to implement
the eviction policy driven freeing of cachekeys).
WARINIG: I am far to be a cocoon expert. I guess
Antonio Gallardo wrote:
Ard Schrijvers escribió:
Thx!!
You do not happen to know where the JCSDefaultStore went in trunk..?? I read
some stuff about it outperforming ehcache in almost every way (and that it
might be easier to implement the eviction policy driven freeing of
cachekeys).
/snip
If there are better alternatives to ehcache we should consider them of
course. Personally I would like that this work will be done in trunk
only. We could build an own maven project for each cache
implementation
which will reduce the dependencies for a user and makes
Ard Schrijvers escribió:
/snip
If there are better alternatives to ehcache we should consider them of
course. Personally I would like that this work will be done in trunk
only. We could build an own maven project for each cache
implementation
which will reduce the dependencies for a user
