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

RE: Interaction of DAV:auto-version and DAV:checkout-fork

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Sun, 28 Jul 2002 16:46:10 +0200
To: "Clemm, Geoff" <gclemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCGEJDFAAA.julian.reschke@greenbytes.de>

> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
> Sent: Sunday, July 28, 2002 3:00 PM
> To: ietf-dav-versioning@w3.org
> Subject: RE: Interaction of DAV:auto-version and DAV:checkout-fork
> The only behavior that seems to me to be consistent with the standard
> is (a), rejecting the request.  The only way that CHECKOUT can succeed
> on a version that has DAV:checkout-fork as DAV:discouraged, and already
> has a successor, would be if the CHECKOUT had a DAV:fork-ok argument,
> and there is no way for a versioning-unaware client to add a DAV:fork-ok
> argument to the auto-checkout.

Well, the spec doesn't say anything about the type of checkout that is
automatically performed. Not saying anything doesn't mean that anything
different than a "default" CHECKOUT is forbidden, right=

So I think it would be compliant to default to a CHECKOUT *with*
DAV:fork-ok, however I personally wouldn't do that.
Received on Sunday, 28 July 2002 10:47:16 UTC

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