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

RE: auto-checkout and auto-checkin

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 17 Jul 2001 04:56:14 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B103A389DC@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
   > From:  Jim Amsden
   > > If the DAV:auto-version value is DAV:checkout, when a 
   > > modification request is applied to a checked-in 
   > > version-controlled resource, the request is automatically 
   > > preceded by a checkout operation.

   > How would a non-versioning aware client check this back in? 

   From: John Hall [mailto:johnhall@evergo.net]

   They wouldn't.

That is correct.  The checkin would have to be done by a 
versioning-aware client.

   I don't think we should define that state.  It is
   there because it mimic's the effect of the old
   auto-checkout-unlocked without an auto-checkin-unlocked.

This state is required for an important baseline use case.  In
particular, DAV:checkout will commonly be the DAV:auto-version value
for version-controlled configurations.  This allows a basic versioning
client to modify a version-controlled member of a baseline-controlled
collection (i.e. CHECKOUT/CHECKIN, UPDATE, MERGE) without creating a
new baseline for every CHECKIN/UPDATE/MERGE.  An advanced versioning
client would then be used to create a new baseline (by checking in the
version-controlled configuration).

Received on Tuesday, 17 July 2001 04:48:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:47 UTC