I went down the road of thinking of eviction as also being about invalidation, and created an algorithm for performing timed expiration, but JBoss Cache expiration is really just the lowly task of managing memory.
Anyway, in addition to "when" "which" and "how many" I'd like to see "in what way" added to the list of concerns. Typically, people want to do "page to disk", but I can imagine wanting plain removal, or migration, or compression perhaps. (Background compression would be a neat feature, come to think of it.)
And in terms of invalidation, some sort of general "invalidation" interceptor would be nice to see that checked the validity of the data being fetched. This is likely necessary since the eviction thread might not be work soon enough.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080197#4080197
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080197
I thought it might be worthwhile sometime back to introduce various attributes such as read-only or hidden to a Node by potentially utilizing something like the EnumSet. Having a flag mechanism accomplishes a few things: Reduces future changes of the Node interface (no need to add methods for a new feature), and reduces node memory size (no need to add new boolean variables).
I really think that how POJO Cache manages internal information is ugly. Having FQN with names such as "jboss_internal" etc. and doing all sorts of FQN hackery is really suggestive there must be a better way.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4080195#4080195
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4080195