Next message: Clemm, Geoff: "RE: Members of a collection"
Message-ID: <65B141FB11CCD211825700A0C9D609BC01FA5219@chef.lex.rational.com>
From: "Clemm, Geoff" <gclemm@Rational.Com>
To: ietf-dav-versioning@w3.org
Date: Wed, 16 Feb 2000 22:44:42 -0500
Subject: RE: Auto version for workspaces
I'm not averse to adding a DAV:auto-version field to a
workspace resource, but just to make sure we're on the
same page, this doesn't give a versioning-unaware client
any more power (if it can set DAV:auto-version on the
default workspace, it can set it on a versioned resource).
Also (as currently defined), the DAV:auto-version property
only has effect on versioning-unaware clients (i.e. ones
that do not know to use Workspace or Version-Selector
headers), so this property only has an effect when the
specified workspace is the default workspace for accessing
the versioned resource, and when no Workspace or Version-Selector
header is specified in the request.
So what this really provides is a way for a versioning aware
client to effectively set DAV:auto-version for a whole set of
versioned resources.
Tim: Is this still what you wanted?
Cheers,
Geoff
> -----Original Message-----
> From: Tim_Ellison@oti.com [mailto:Tim_Ellison@oti.com]
>
> I think it would be a fine thing if workspaces had an auto
> version property
> (along the lines of the resource property) that indicated
> that all resources
> PUT through that workspace were auto-versioned. This would
> allow down-level
> clients to interact on a level playing field, rather than
> relying on their
> versioning chums to set the flag on a per resource basis.
>
> If I were Geoff, I'd say that I'll add it to the spec unless anyone
> complains :-)
>
> Tim
>