I think it's way too early to discuss removing FineGrainedAtomicMap and
AtomicMap, as long as we don't have a concrete alternative with similar
properties.
Cache.getGroup(groupName) is just a method name at this point, we don't
have any idea how it will compare to AtomicMap/FineGrainedAtomicMap from a
transaction isolation or performance perspective. BTW, do we really need
the group name to be a String?
A good way to prove that the grouping API is a proper replacement for the
atomic maps would be to replace the usage of atomic maps in the Tree module
with the grouping API. Unless we plan to drop the Tree module completely...
Cheers
Dan
On Wed, Jan 22, 2014 at 2:45 PM, Mircea Markus <mmarkus(a)redhat.com> wrote:
On Jan 21, 2014, at 8:42 PM, Vladimir Blagojevic <vblagoje(a)redhat.com>
wrote:
> I agree with Erik here. Deltas are used in M/R and I've never detected
> any problems so far.
> On 1/21/2014, 1:39 PM, Erik Salter wrote:
>> Please don't remove the Delta stuff. That's quite useful, especially
for
>> large collections.
+1 to keep DeltaAware. Thanks for the feedbak
>>
>> Erik
>>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
Cheers,
--
Mircea Markus
Infinispan lead (
www.infinispan.org)
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev