Re: auto-version and shared write-locks

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
> 
>