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

Re: auto-version

From: Geoffrey M. Clemm <geoffrey.clemm@rational.com>
Date: Thu, 11 Jan 2001 17:56:07 -0500 (EST)
Message-Id: <200101112256.RAA10078@tantalum.atria.com>
To: ietf-dav-versioning@w3.org

   From: "Vasta, John" <jvasta@rational.com>

   > > While I'm in there, Jim Amsden asked if we could add a
   > > value to DAV:auto-version that says "only auto version
   > > while locked" (i.e. this would say to auto-checkout if
   > > the checked-in vcr is write-locked, but just fail the
   > > update if it is not write-locked).
   > It should not be added. I don't have locking in my server, so
   > adding that to the spec would mean that I couldn't ever
   > auto-version.

   Not quite right; it's up to the client to set the DAV:auto-version
   property (your server can default the value to whatever it
   wants). So it would only mean that your server couldn't support
   clients that wished to assert this policy.

That is correct.  The protocol explicitly warns clients that servers
may refuse to allow the client to modify the value of DAV:auto-version
(this appears in the definition of DAV:auto-version).

I believe that both kinds of servers will be written (i.e. servers
that will always auto-version, and others that only auto-version on a
locked resource lock), and that it would be good to define an
interoperable way for a client to find out what kind of server it is
running against.

So with that clarification, is this OK with you Greg (and everyone else)?

Received on Thursday, 11 January 2001 17:56:58 UTC

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