memcacheddotnet-devel

[Memcacheddotnet-devel] no write locks?

[John S. <joh...@gm...>]

Hi,

Looking at the client code there doesn't seem to be any object
locking/concurrency checking. Wondering if this is on purpose and left as an
exercise for specific implementations?
For example, in the middle of a thread calling set() on a large object, what
prevents the half updated object from being fetched by another reader
thread?
Are there locks on memcached? (win32 port)

Thanks,
John

Re: [Memcacheddotnet-devel] no write locks?

[John S. <joh...@gm...>]

Tim,

Thanks for the clarification. I should have known something like that
wouldn't be neglected by the server. Didn't they teach in school that it
would be impractical to lock down resources on the client side.
Heh, my college Networks prof would have a fit if he heard me ask this.

John

On Nov 12, 2007 8:50 PM, Tim Gebhardt <ti...@ge...> wrote:

> Hi John,
>
> Locking is handled by the memcached server.  I believe it does optimistic
> locking concurrency, but a quick check on the memcached homepage will
> confirm that.
>
> -Tim Gebhardt
> ti...@ge...