[JBoss-dev] [JBossCache] - Re: timed expiry

2005-01-30 Thread [EMAIL PROTECTED]
Our design of eviction policy is not based on per-node basis. Rather it is per-region. Nonetheless to create *roughly* what you want to achieve, it still can be done through the current eviction policy framework. Couple things need to happen though: 1. Region parameters will need to be

[JBoss-dev] [JBossCache] - Re: timed expiry

2005-01-28 Thread tcherel
Eviction policy is what you are looking for, I think. JBossCache provides a default LRU implementation. the time-to-live is not set per object you insert in the cache, but per region. Check eviction policy in JBossCache documentation. Thomas View the original post :

[JBoss-dev] [JBossCache] - Re: timed expiry

2005-01-28 Thread analogueboy
sorry, should have been clearer, i was asking if a time-based eviction policy would be added. I've looked thru the api and I can't see any references to the time that an FQN is added, so I suppose it would have to be maintained separately, ie listen for the creation/update of a node and log the

[JBoss-dev] [JBossCache] - Re: timed expiry

2005-01-28 Thread tcherel
I think this can be all implemented as an eviction policy. The only thing that cannot be implemented using the eviciton policy is the ttl per node, unless you come up with a specific nming convention for the node and provide the ttl in some other ways (such as through the configuration of your