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 time. Then a timertask could revise a region and look at the time that the node was added, compare it to the ttl on the node, and evict the node if necessary.
The only problem is that this requires adding the ttl param to the put() method, and maintaining the time that that node was created. As I said before, we have coded this internally, but it depends on other libraries (namely quartz and spring) as the timer. We've extended treeCache to add the params needed and then set up quartz using spring. Do other people see the value in this, and would people be happy with those dependencies? The benefit of having ttl on nodes is that you can achieve the same functionality as oscache in the web tier, using filters and taglibs with timeouts which is really useful. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3864130#3864130 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3864130 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
