W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > January to March 2002

Re: LOCK/UNLOCK or CHECKIN/CHECKOUT

From: Tim Ellison <Tim_Ellison@uk.ibm.com>
Date: Thu, 10 Jan 2002 14:34:02 +0000
To: ietf-dav-versioning@w3.org
Message-ID: <OF8D5C40A7.2B487EA8-ON80256B3D.004F377B@portsmouth.uk.ibm.com>
Elodie,

> I'd like to know whether I well understood : the  mechanism of 
checkout-put-checkin
> cretes a new version of a resource,

correct -- indeed the version is a resource, so checking-in creates a new 
version resource.

> while the  lock-unlock mechanism allows to modify a resource without 
creating a new
> version, is that right ?

this is also correct.  Locking a resource just causes a state change in 
the locked resource; it does not create any other resources.

> Can someone explain me the exact difference between  this two mechanisms 
?
 
Locking is typically used in a multi-user environment.  Obtaining a lock 
permits you to modify a resource and prevents others from modifying the 
resource.  This allows you to ensure others' contents are not overwritten, 
and you can set consistent content and dead properties for example.
Checking out and in are used to capture a meaningful state of a resource 
as a version.  It is meaningful to do this in single or multi-user 
environments.  The captured states can be 'viewed' or restored at some 
later time.

Locking and versioning are separate concepts.

Regards,
Tim
Received on Thursday, 10 January 2002 09:43:17 GMT

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