Sounds very logical. What does it do now?
jbosscache-dev-bounces(a)lists.jboss.org wrote:
Looks like Cache.getRegion(Fqn fqn) is the one that is most
convenient to use (since activate region should not be in the
responsibility of CacheSPI). But I am thinking to refine the
contract of getRegion(Fqn fqn) such that if I have previously
defined a parent region, say, "/person". Then doing a call
getRegion("/person/joe") should still return the parent
region associated with "/person". I think this is the
logical. What do people think?
Thanks,
-Ben
-----Original Message-----
From: jbosscache-dev-bounces(a)lists.jboss.org
[mailto:jbosscache-dev-bounces@lists.jboss.org] On Behalf Of Ben Wang
Sent: Thursday, October 05, 2006 12:49 AM
To: jbosscache-dev(a)lists.jboss.org
Subject: [jbosscache-dev] RegionManager
Manik,
Currently, we have Cache.getRegion and also
CacheSPI.getEvictionRegionManager and
CacheSPI.getRegionManager APIs. It seems that these two are a
bit redundant in that one can also create a region from
CacheSPI call. So what is the intention here?
Thanks,
-Ben
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
Ph: 510-396-3864
skype: bstansberry