W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

RE: Problems with locking and DeltaV resources

From: Clemm, Geoff <gclemm@rational.com>
Date: Fri, 10 Aug 2001 12:33:06 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103DED62A@SUS-MA1IT01>
To: DeltaV <ietf-dav-versioning@w3.org>
It is likely that a server that supports working resources will
have ACL's on the working resource that only allows modification
of the working resource by the principal that created the working
resource.  Also, another client is extremely unlikely to encounter
the working resource, since it has been given a new (virtually
guaranteed to be obscure) URL.  So the window between when the
working resource is created and when the working resource is locked
is likely to be of extremely low risk.

Cheers,
Geoff 

-----Original Message-----
From: Lisa Dusseault [mailto:lisa@xythos.com]
Sent: Wednesday, August 08, 2001 8:55 AM
To: DeltaV
Subject: Problems with locking and DeltaV resources



Let's say as a client I want to protect my version-controlled resource (VCR)
and associated working resource (WR) from being edited by other users while
I check it out and edit it.  One might think the user could issue:

 - LOCK VCR
 - CHECKOUT VCR
 - LOCK WR
 ...

This won't work, however.  There is a window when other users can lock my
WR, edit it, etc, before I manage to lock it.   Having another client "take
over" my WR is a situation which I think most clients will want to prevent,
or will not know how to handle, or both.

Any way of dealing with this?

lisa
Received on Friday, 10 August 2001 12:24:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT