[infinispan-dev] Per-entry lock container

[Jason Greene]

Sent from my iPhone

On Oct 16, 2012, at 10:39 AM, Jason Greene <jason.greene at redhat.com> wrote:

>> from _get_ to lock on an eventually created new instance.
> 
> Yes if you get the ordering right, it can certainly be done. You might have to introduce a state-based CAS or secondary lock though for some scenarios (I haven't thought through them all) I think Manik's point though was just that getting it right is harder than just making the whole thing atomic.

Although there is no way out of the remove, you still have to recheck the lock is valid after every successful aquire, and then try to lock the new lock