Re: MV Keys

From: mAsterdam <mAsterdam_at_vrijdag.org>
Date: Sat, 04 Mar 2006 17:11:35 +0100
Message-ID: <4409bc36$0$11061$e4fe514c@news.xs4all.nl>

vc wrote:
> mAsterdam wrote:
> [...]
>

>>Extrapolating, ISTM your answer to the question:
>>"could this removeAt operation possibly be useful
>>in a concurrent environment?" would be
>>that it is irrelevant:
>>removeAt(index) isn't even valid under concurrency.
>>
>>Am I understanding your point correctly?

>
>
> No. The concurrency is irrelevant thanks to the CC's ensuring that the
> concurrent execution result is equivalent to some serial execution of
> the same transactions. It does not matter what kind of write
> operations you want to have in your database.

"The concurrency is irrelevant"
In this case this goes to say 'It doesn't matter wether there is concurrency or not, the effect of OurSharedList.removeAt(3) is the same.'

What should the effect of OurSharedList.removeAt(3) be? Received on Sat Mar 04 2006 - 10:11:35 CST