[jbosscache-dev] REPEATABLE_READ and write skews

[Manik Surtani]

Ah, there's the disconnect - I've called the cfg option:

	# if true, allows any write skews detected to proceed without  
throwing an exception
	allowWriteSkew = true

But I think that can be confusing - writeSkewCheck is better.

On 16 Jul 2008, at 02:31, Jason T. Greene wrote:

> Right, what I meant was:
>
> # Prevents writes to a node that changed after it was read
> write-skew-checking = false
>
> Manik Surtani wrote:
>> I'm guessing you mean allow write skews by default, rather than  
>> throw an exception when they are detected?
>> On 15 Jul 2008, at 23:14, Jason T. Greene wrote:
>>> IMO we should default it to off, since enabling it is a step  
>>> closer to SERIALIZABLE. Having it off still offers greater  
>>> isolation than most dbs, which are all read committed essentially.
>>>
>>> Manik Surtani wrote:
>>>> Should write skews be allowed by default?  This would be less  
>>>> correct, but less likely for exceptions being thrown due to  
>>>> concurrent read-then-write patterns.
>>>> What do you guys think?
>>>> - Manik
>>>> -- 
>>>> Manik Surtani
>>>> Lead, JBoss Cache
>>>> manik at jboss.org
>>>> _______________________________________________
>>>> jbosscache-dev mailing list
>>>> jbosscache-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>>>
>> -- 
>> Manik Surtani
>> Lead, JBoss Cache
>> manik at jboss.org
>

--
Manik Surtani
Lead, JBoss Cache
manik at jboss.org