W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1999

RE: One lock per resource per person?

From: Chris Kaler (Exchange) <ckaler@Exchange.Microsoft.com>
Date: Mon, 1 Nov 1999 15:00:09 -0800
Message-ID: <FD7A762E588AD211A7BC00805FFEA54B041DDAA7@HYDRANT>
To: "'Geoffrey M. Clemm'" <gclemm@tantalum.atria.com>, w3c-dist-auth@w3.org
But my client may use shared locks to coordinate updates.  The 
client app doesn't recognize principals...

-----Original Message-----
From: Geoffrey M. Clemm [mailto:gclemm@tantalum.atria.com]
Sent: Tuesday, October 19, 1999 7:57 PM
To: w3c-dist-auth@w3.org
Subject: Re: One lock per resource per person?

   From: "Chris Kaler (Exchange)" <ckaler@Exchange.Microsoft.com>

   <ck/> Using SCC systems today, I can
	 create multiple shared locks against the same resource.  In
	 general you can do this by "checking it out" multiple times, but
	 the basic notion is that I may be engaged in parallel activities
	 at my client even though I am the same principal.

It's very important to distinguish "multiple checkouts" from "shared
locks".  Multiple checkouts are safe and do not suffer from any lost
update problem.  Shared write locks are not safe, and you are
susceptible to getting your update's trashed by anyone else that
shares that lock.

Received on Monday, 1 November 1999 18:00:21 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:01:20 UTC