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

Locks and Moves

From: Kevin Wiggen <wiggs@wiggenout.com>
Date: Tue, 18 May 1999 13:34:53 -0700
Message-ID: <068d01bea16d$e2be92c0$fad466d8@pacbell.net>
To: <w3c-dist-auth@w3.org>
Sorry if this is answered somewhere, I couldn't find it...

1) Section 8.10.4 "If the lock cannot be granted to all resources, a 409 (Conflict) status code MUST be returned with a response entity body containing a multistatus XML element describing which resource(s) prevented the lock from being granted."  

  Then in example 8.10.10, a LOCK fails but gives a 207 response code in the header.  What is the proper response code??

2)  If a more than one user has a share lock on a resource, they can all WRITE to it, but can they DELETE it???  If resouce /C/B exists, and user FOO and user BAR both have their own shared lock of /C/B, what happends if FOO issues a DELETE?  Will the DELETE succeed thus removing the share lock FOO AND BAR have on /C/B (but possibly leaving the lock on /C if /C/B was part of a depth=INFINITY lock), or will the DELETE fail??

3)  During a COPY or MOVE, if the file/directory exists, and the overwrite flag = Y.  What happends if the DELETE portion fails??  Should the MOVE/COPY fail giving the errors for the DELETE, or should the server still try to do the MOVE/COPY to the location where the DELETE failed??  And what is the proper response status (and XML) to return to the client in this case?

Thanks,
Kevin
Received on Tuesday, 18 May 1999 16:38:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:49 GMT