Re: CHECKOUT target selector
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Mon, 20 Dec 1999 13:48:41 -0500
Date: Mon, 20 Dec 1999 13:48:41 -0500
Message-Id: <9912201848.AA07660@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <8525684D.00641856.00@d54mta03.raleigh.ibm.com>
Subject: Re: CHECKOUT target selector
I agree with Jim that this will not be very common, since if the
workspace doesn't select the predecessor when it is checked out, then
it is likely to not select the new revision when it is checked in.
For those times when you do need to check out a revision that is not
currently selected by the workspace, your client can just use the
workspace independent URL for that revision.
Cheers,
Geoff
From: jamsden@us.ibm.com
If the target-selector and the workspace for the checked out working
resource are not the same, then the updates will become invisible when the
resource is checked in. This doesn't necessarily mean we don't want to
allow this, but it isn't a useful use case.
Tim_Ellison@oti.com (Tim Ellison OTT)@w3.org on 12/20/99 11:30:20 AM
Presently, the CHECKOUT method uses the Target-Selector to specify the
workspace in which to create the working resource.
I propose the workspace be defined in the CHECKOUT body so that the
Target-Selector can remain useful for selecting the revision.
The case in point is attempting to CHECKOUT a particular revision by a
revision ID, workspace RSR or label -- where would you specify such
information?
Comments?