[infinispan-dev] possible bug in TreeCache.put(Fqn fqn, Map<? extends K, ? extends V> data) when passed an empty map

[Galder Zamarreño]

On Sep 14, 2010, at 12:49 PM, Manik Surtani wrote:

> 
> On 14 Sep 2010, at 11:08, Galder Zamarreño wrote:
> 
>>> 
>>> Are you referring to not locking a node when adding or removing a child node?
>> 
>> This comes from a conversation we had online where I was checking whether there was a real need for TreeCache in this use case.
> 
> Right, I thought Scott said he wanted weaker consistency.
> 
>> 
>> IIRC, parents used to be locked for writing when adding/removing children. Looking at the Infinispan code, this might not be the case any more:
>> 
>>            // don't lock parents for child insert/removes!
>>            icc.getInvocationContext().setFlags(Flag.SKIP_LOCKING);
>>            parentStructure.put(fqn.getLastElement(), fqn);
>> 
>> I see we don't have anything in http://community.jboss.org/wiki/Infinispan wrt the tree module. I think it'd be interesting to explain what the lock semantics are in the tree module and how different these are with JBoss Cache. Thoughts?
> 
> +1.  Care to make some notes on this on the wiki?

Yup, I'll get around to this: https://jira.jboss.org/browse/ISPN-651

> 
> Cheers
> Manik
> 
> --
> Manik Surtani
> manik at jboss.org
> Lead, Infinispan
> Lead, JBoss Cache
> http://www.infinispan.org
> http://www.jbosscache.org
> 
> 
> 
> 
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache