<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Sanne,<div><br></div><div>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. </div><div>The eager locking is not handled indeed, but single node lock acquisition for eager locking is already available: <a href="http://community.jboss.org/wiki/LockingAndConcurrency#Locking_a_single_remote_node">http://community.jboss.org/wiki/LockingAndConcurrency#Locking_a_single_remote_node</a></div><div>Can you please take a look and let me know if there are aspects of 5 that are not covered by 2&4? </div><div><br></div><div>Cheers,</div><div>Mircea</div><div><br></div><div>[1] <a href="http://community.jboss.org/wiki/PossibleLockingImprovements">http://community.jboss.org/wiki/PossibleLockingImprovements</a></div></body></html>