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

RE: Feature request for CHECKIN/OUT extension

From: Julian F. Reschke <julian.reschke@greenbytes.de>
Date: Tue, 7 Aug 2001 11:54:44 +0200
To: "John Hall" <johnhall@evergo.net>
Cc: <ietf-dav-versioning@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCOECNCNAA.julian.reschke@greenbytes.de>
> From: ietf-dav-versioning-request@w3.org
> [mailto:ietf-dav-versioning-request@w3.org]On Behalf Of John Hall
> Sent: Tuesday, August 07, 2001 12:12 AM
> To: 'Julian F. Reschke'
> Cc: ietf-dav-versioning@w3.org
> Subject: RE: Feature request for CHECKIN/OUT extension
> Well, I personally expect the CHECKIN URI to be the same as the CHECKOUT
> URL.

When using the checkout-in-place feature, the URI of the VCR (that the
client is editing) will not be the same as the URI of the version that is
created upon CHECKIN, right?

> Note that when using working resources (where this is a concern) that we
> have a proposal with the following characteristics:

Maybe there was a misunderstanding here -- I was proposing this for
checkout-in-place, not for working resources.

> A CHECKOUT of a VCR with a <apply-to-version> will cause the working
> resource to track the VCR from which it came, and a subsequent CHECKIN
> of the working resource will checkin the working resource and update the
> vcr.
> That seemed to be what you were after, or did you hope for a broader
> ability to do something like this?

It doesn't provide the client the ability to display / insert the URI of the
version that *will* be created upon CHECKIN into the document, or am I
missing something?
Received on Thursday, 9 August 2001 06:31:05 UTC

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