[infinispan-dev] lock improvement #5

[Manik Surtani]

Are you suggesting #5 is superfluous and not needed?

On 23 May 2011, at 10:58, Mircea Markus wrote:

> Hi Sanne,
> 
> Looking at you're ideas around "Replicated Keys & Values, non-replicated Locks" [1]: acquiring a single lock, disregarding of numOwners, is covered in 2(non transactional) and 4(transactional): both suggest an approach for acquiring lock on a single node to avoid deadlocks. 4 also suggest an approach to fail-over the lock to the new owner. 
> The eager locking is not handled indeed, but single node lock acquisition for eager locking is already available: http://community.jboss.org/wiki/LockingAndConcurrency#Locking_a_single_remote_node
> Can you please take a look and let me know if there are aspects of 5 that are not covered by 2&4? 
> 
> Cheers,
> Mircea
> 
> [1] http://community.jboss.org/wiki/PossibleLockingImprovements
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Lead, Infinispan
http://www.infinispan.org



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20110609/05d75dfb/attachment-0001.html