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

RE: DeltaV doesn't support a true client workspace

From: Lisa Dusseault <lisa@xythos.com>
Date: Sat, 3 Feb 2001 16:03:23 -0800
To: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>, <ietf-dav-versioning@w3.org>
Message-ID: <CNEEJCPIOLHKIOFNFJDPGEPFCCAA.lisa@xythos.com>
> Everyone else: Do you think that the Autoversion header for PUT is
> of sufficient value to be worth putting into core?  It is a way
> for a versioning client to interact with a server like Chuck's
> without forcing his server to have every PUT to a version-controlled
> resource result in a new version.

I think this header could be extremely valuable, particularly if it
could indicate either T or F.

Example: if the DAV:auto-version property indicates that auto-versioning
is off, the presence of an "Auto-version: T" header would override and
create a new version.  Also, if the DAV:auto-version property indicates
that auto-versioning is on, but the client sends "Auto-version: F"
header in the request, then the server can know it's a work-in-progress
and just modify the latest version, without requiring a checkout/checkin
or changing the version URL.

Would it be less confusing to have the header called
"Create-new-version" or some such?

lisa
Received on Saturday, 3 February 2001 19:05:04 GMT

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