- From: John Hall <johnhall@evergo.net>
- Date: Sat, 14 Jul 2001 13:43:53 -0700
- To: "'Clemm, Geoff'" <gclemm@rational.com>, <ietf-dav-versioning@w3.org>
Geoff took care of my concerns. I withdraw my proposed modifications. I believe the solution works for us. > From: ietf-dav-versioning-request@w3.org > [mailto:ietf-dav-versioning-request@w3.org] On Behalf Of Clemm, Geoff > From: John Hall [mailto:johnhall@evergo.net] > > > A client can do this by creating a non-auto-update working > resource by checking out the appropriate version, copying the > auto-update working resource to the new working resource, and > then checking in the non-auto-update working resource. I > believe keeping the auto-update property protected (i.e. not > modifiable by a client) is more important than saving a round > trip in this recovery use case. OK -- Fine with me. > 3) The new precondition is designed to let a client know > that a server > ONLY supports WORKING-RESOURCES with the auto-update feature. > > This can already be made clear by having CHECKOUT not appear > in the DAV:supported-method-set of a version resource, and > having a 405 response if CHECKOUT is applied to a version resource. Ok, I'll do it that way. Once I look up what a 405 code is, since I'm new to this.
Received on Saturday, 14 July 2001 16:43:54 UTC