Is this covering a different use case than having two caches k1 and k2 equally configured?
My current app Scarlet is dynamically creating many different caches using the configuration names asd templates, I'm happy with that.

Il giorno 19/mag/2010 16:43, "Manik Surtani" <manik@jboss.org> ha scritto:


On 13 Apr 2010, at 11:01, Manik Surtani wrote:

>

> On 13 Apr 2010, at 10:50, Sanne Grinovero wrote:
>
>> rightfull concern, I wouldn't personally ha...

Here is an alternative - *do* we want to support scoping?  By this, I mean:

cache.withAffinityKey("k1").put("name", "Manik");
cache.withAffinityKey("k1").put("country", "UK");

cache.withAffinityKey("k2").put("name", "Sanne");
cache.withAffinityKey("k2").put("country", "IT");

will be allowed and the two will not overwrite each other, *but* you cannot retrieve stuff by simply doing:

cache.get("name") anymore.  You would have to do:

cache.withAffinityKey("k1").get("name").  Simply doing a cache.get("name") will return a null.

What do people prefer?

Cheers
Manik


--
Manik Surtani
manik@jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http:...