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

RE: auto-checkout and auto-checkin

From: Lisa Dusseault <lisa@xythos.com>
Date: Thu, 12 Jul 2001 10:15:37 -0700
To: "Tim Ellison" <Tim_Ellison@uk.ibm.com>, "DeltaV" <ietf-dav-versioning@w3.org>
> It was simpler, but some folk complained that their use case was not
> satisfied by it.  I recall the "make the lifetime of the
> check-out the same
> as that of the lock" as a reasonable request, but the others I forget.

Then let's clearly identify the use cases and satisfy them, or at least the
important ones.  The current spec for the behaviour has now allowed for
THREE independent interpretations (Tim's, John's, mine) and puts a
horrendous burden on the client to understand the effect of any possible
combination that the server might have for these two properties and their
three or four possible values.

I know of two use cases so far that I believe people are actually going to

A.  No auto-versioning is done.
B.  Server auto-versions once for every lock/unlock that included at least
one write operation.  Server auto-versions once for every write operation
that isn't part of a lock.

I recall there was at least one other in way this used to be done (before
breaking it into two separate properties), but I don't have an old version
of the draft handy.

Received on Thursday, 12 July 2001 13:15:59 UTC

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