In a sense, yes. Remember, this would be implemented by putting stuff with related
affinity in an AtomicHashMap and storing the AHM under the affinity key.
I implemented the tree adapter in a very similar way. :)
On 20 May 2010, at 19:04, Sanne Grinovero wrote:
So if I understand it correctly this is a proposal for a simplified
tree API?
Il giorno 19/mag/2010 19:55, "Manik Surtani" <manik(a)jboss.org> ha
scritto:
On 19 May 2010, at 17:35, Sanne Grinovero wrote:
> Is this covering a different use case than havin...
Slightly different. Scoping could be useful for use cases where creating a cache per
scope is too expensive. E.g., I want to cache a person's name, address and
photograph. I could do this:
cache.put("person1_name", name);
cache.put("person1_address", address);
cache.put("person1_pic", pic);
cache.put("person2_name", name);
cache.put("person2_address", address);
cache.put("person2_pic", pic);
cache.put("person3_name", name);
cache.put("person3_address", address);
cache.put("person3_pic", pic);
and every time I need to retrieve anything I need to concatenate person_id with the
"field" I am interested in. It would be too expensive to create a separate
cache per person, as the system may have thousands of users.
> >
> >> Il giorno 19/mag/2010 16:43, "Manik Surtani"
<manik(a)jboss.org> ha scritto:
> >>
> >>
> >> On 13 Apr 2...
>
> > _______________________________________________
> > infinispan-dev mailing list
> > infinispan-dev@lis...
>
--
Manik Surtani
manik(a)jboss.org
Lead, Infinispan
Lead, JBoss Cache
http://www.infinispan.org
http://www.jbosscache.org
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev