Next message: Clemm, Geoff: "RE: Extending Target-Selector"
From: jamsden@us.ibm.com
To: Tim_Ellison@oti.com (Tim Ellison OTT)
cc: ietf-dav-versioning@w3.org
Message-ID: <85256895.00786E55.00@d54mta03.raleigh.ibm.com>
Date: Wed, 1 Mar 2000 16:55:16 -0500
Subject: Re: Disappearing CHECKINs
The workspace has a current label property this is automatically applied to
the resource when it is checked in. This label should be in the workspace
revision selection rule. If the client is using activities, the current
activity can play this same role.
If the workspace is being used as a checkout token, then the client is
completely responsible for all revision selection and would have to know
the stable URLs to do this. I think at the last design team meeting we
agreed that these URLs would be returned by versioning methods that created
them.
|------------------------+------------------------>
| | Tim_Ellison@oti.com |
| | (Tim Ellison OTT) |
| | Sent by: |
| | ietf-dav-versioning-r|
| | equest@w3.org |
| | |
| | 03/01/2000 04:04 PM |
| | |
|------------------------+------------------------>
>------------------------|
| |
| To: |
| ietf-dav-versioning@w|
| 3.org ('Delta V') |
| cc: |
| Subject: |
| Disappearing CHECKINs|
>------------------------|
It would seem useful to return the stable URL of resources from a number of
operations, including CHECKIN, since if the revision that was CHECKIN'ed is
not selected by the workspace then it disappears.
A workspace that selects purely on labels for example would be in trouble.
They can't label the working resource, and after CHECKIN the revision has
to be found via the versioned resource revision-set to be labeled.
Tim