Re: [infinispan-dev] First working version of lock/unlock API

On 12 May 2009, at 21:36, Vladimir Blagojevic wrote: By way of tests you want to make sure: 1. Concurrent non-tx writes on the same node are held back by the lock 2. Concurrent non-tx writes on a different node are held back by the lock 3. As 1 but with concurrent tx writes 4. As 2 but with concurrent tx writes 5. Test that locks are released on commit even if there is no explicit unlock() 6. As 5 but with rollback 7. Test that locks are released on unlock if the key is not modified in the tx 8. Test that locks are NOT released despite unlock if the key is modified in the tx. Should only unlock on commit/rollback in this case. The above should also be tested with Invalidation as well as Distribution. And of course then there is the implicit eager locking on transactions, as you mention. :-) -- Manik Surtani manik(a)jboss.org Lead, Infinispan Lead, JBoss Cache http://www.infinispan.org http://www.jbosscache.org