Re: CHECKOUT target selector
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Mon, 20 Dec 1999 13:58:02 -0500
Date: Mon, 20 Dec 1999 13:58:02 -0500
Message-Id: <9912201858.AA07677@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
In-Reply-To: <1999Dec20.134100.1250.1423435@otismtp.ott.oti.com>
Subject: Re: CHECKOUT target selector
From: Tim_Ellison@oti.com (Tim Ellison OTT)
>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.
I'm thinking of the case, for example, where I want my working resource base
on a labeled revision even though the workspace always selects the "latest"
revision (or latest in an activity,...)
Just as a note, if your workspace is looking at the latest in an activity,
and you check out an arbitrary revision, then your checkin will fail
unless the revision you checked out happened to be a descendent of the
latest revision in that activity.
I need to represent "check out revision labeled 'foo' into
/myworkspace"
there is no way to do this at present.
I agree that cross-workspace checkout is less useful but not infeasible.
In this case, I think it is reasonable to require that the client
first obtain the workspace-independent URL for the revision.\
Cheers,
Geoff