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

RE: why URL protection is not feasible when you version collectio ns

From: Jim Whitehead <ejw@ics.uci.edu>
Date: Wed, 27 Oct 1999 13:37:07 -0700
To: w3c-dist-auth@w3.org
Message-ID: <NDBBIKLAGLCOPGKGADOJCEJGCHAA.ejw@ics.uci.edu>
Well, I actually tried to move the parent collection of a locked resource
using some existing DAV tools, and here's what happened:

User A: Opens document "/ejw/fun/survey.doc" with Word 2000. This locks the
document.

User A then goes and opens up Web folder on the desktop, displaying "/ejw/".
User A then asks to rename folder "fun" to "notfun". An error message comes
back, stating that the folder couldn't be renamed, but after manually
refreshing the Web folder, it appears that a new folder "notfun" and the old
folder "fun" are both still present. When the "fun" folder only contains
"survey.doc", after the rename both folders contain distinct copies of
"survey.doc".

When "fun" contains more resources than just "survey.doc" before the move,
the destination folder only contains these other resources, and does not
contain "survey.doc" (Xythos), or contains all resources, including
"survey.doc" (IIS 5 Beta 3). After the move, folder "fun" only contains
"survey.doc".

As I recall from RFC 2518, this is actually compliant behavior -- the move
was performed best-effort.

This suggests that part of the problem is the interplay between the new
binding semantics of move, and the desire to preclude best-effort moves.

- Jim
Received on Wednesday, 27 October 1999 16:37:33 GMT

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