RE: auto-checkout and auto-checkin

Other than mimicing auto-checkout-unlocked, what purpose would this option 
provide? Looks like:
- Versioning aware clients wouldn't need to use it, they can (should?) do 
the checkout
- Non-versioning aware clients could create checked out resources they 
can't check back in

What's the use case?





"John Hall" <johnhall@evergo.net>
07/17/2001 03:40 AM

 
        To:     "'Jim Amsden'" <jamsden@us.ibm.com>, <ietf-dav-versioning@w3.org>
        cc: 
        Subject:        RE: auto-checkout and auto-checkin

 

They wouldn't.  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.


> -----Original Message-----
> From: ietf-dav-versioning-reque       st@w3.org 
> [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Jim Amsden
> Sent: Monday, July 16, 2001 5:06 PM
> To: ietf-dav-versioning@w3.org
> Subject: RE: auto-checkout and auto-checkin
> 
> 
> >>
> 
> 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? 
> 
> 
>

Received on Tuesday, 17 July 2001 09:11:11 UTC