Question about eviction policy and regions

[fredatwork]

I'd like to raise a functional question about JBossCache eviction policy of an Aop tree cache, more specifically the max number of nodes inside a region.

Is the maximum nodes of a region of an eviction policy for an aop tree cache:

a/ the maximum number of root nodes you can put in the cache, that is the maximum number of calls to 'putObject' you can make with different frq's at each call,

or,

b/ the maximum number of objets put in the cache, an object being either a local root put in the cache with 'putObject' method, or a dependant object that you can reach from root POJOs.

I cannot answer thie question from the documentation provided by the project.

Fred

[tcherel]

I believe that in the JBoss terminology a Node is the the element identified by a fqn.
When looking at the eviction policy and the TreeCacheListener interface, it seems clear that eviction applies to a node as a whole and not to each individual cached object in the Hashtable of such node).

All that to say that I think that the maximum number of nodes inside a region is the maximum number of unique fqn that you can have under this region (which are not necessarily root nodes: /a/b/c/d/e denotes 5 nodes organized in a hierarchy).

Thomas

[ben.wang]

More accurately, for eviction policy in aop, the maximum number of nodes corresponds to number of objects (and it's graph) under that specifc region.

That is, in aop, if a child object is not of *primitive* type, then a new fqn will be created to deflate the object recursively.

I will put this question into faq.

Thanks,

-Ben

[fredatwork]

Ben,

Good idea to put this the faq.

Could you also explain the functional of region's attribute 'timeToLiveSeconds' as well ?

Fred