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

Re: auto-version and shared write-locks

From: Geoffrey M Clemm <geoffrey.clemm@us.ibm.com>
Date: Thu, 7 Dec 2006 09:49:02 -0500
To: "Chetan Reddy" <chetanreddy@gmail.com>
Cc: ietf-dav-versioning@w3.org, ietf-dav-versioning-request@w3.org
Message-ID: <OFBE1FA872.2A9CB0D3-ON8525723D.005174B3-8525723D.0051A2CE@us.ibm.com>
I'd probably wait until the VCR becomes completely write-lock free.
But one could make a reasonable argument either way.
Note: I've never been a fan of shared locks, so whatever you want to do 
there is fine with me (:-).

Cheers,
Geoff

ietf-dav-versioning-request@w3.org wrote on 12/05/2006 11:37:37 PM:

> 
> >The VCR should auto-checkin when all write locks have been removed.
> 
> Do you mean all write locks present in the request that caused the
> auto-checkout? Or should we wait till the VCR becomes completely
> write-lock free (i.e, till all shared write locks of other users are
> also removed )?  I would think that a new version of a resource is
> ready when all the members who are collaborating on work on that
> resource are done and remove their shared lock. Unless this technique
> is meant to be used as a backup mechanism for individual changes made
> by users collaborating on the resource through shared locks.
> 
> Chetan
> 
> 
Received on Thursday, 7 December 2006 14:51:43 GMT

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