W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > October to December 2000

Change sets and activities

From: Jim Amsden <jamsden@us.ibm.com>
Date: Tue, 12 Dec 2000 22:13:22 -0500
To: ietf-dav-versioning@w3.org
Message-ID: <OF3C33D282.5DDF5B5A-ON852569B4.00112A42@raleigh.ibm.com>
<greg>You've got all kinds of race conditions and stuff going in there to
try and
deal with the problem. Sure, the server knows all of the files that Joe is
going to checkin (through examination of the activity), but it can't do
anything about it until all the files are checked in. Does it say "well,
there is a v7 for this file, but I can't give it to you right now." What if
Joe never comes back? Nancy should have got v7 in that case. Oh, and what
happens with rollback for Joe's failed checkin? Or is that first resource
supposed to fail on checkin because some *other* resource in the activity
is
going to fail in the future.</greg>

I don't think we ever considered DAV:version-names to play this role. We
considered them a way to distinguish revisions that is set by the server
for display purposes, they can't be used to access the version. WebDAV
defines the change set to be the latest versions in an activity. It doesn't
say that all the changes were created at the same time. This moves the
validation of the change set to after checkin, not before. I understand
this might not be ideal.
Received on Wednesday, 13 December 2000 10:55:53 GMT

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