Re: [infinispan-dev] Implicit locking
On 5/25/09 10:49 PM, Manik Surtani wrote:
> Not so much. It is easier to do it from TxInterceptor I think. In
> overridden enlistWriteAndInvokeNext we create LCC instances and pass
> the along the chain. We will slightly change
> LockIterceptor#visitLockControlCommand to handle these specific cases
> - not so hard.
Ok
How about making a new interceptor - ImplicitEagerLockingInterceptor
that we put after TxInterceptor in case useEagerLocking is true? This is
easiest and cleanest implementation wise and easy to maintain in the
long run. It would work out of the box for all replication types.
WDYT?