Next message: Tim Ellison/OTT/OTI: "Re: Stable Href's of collections"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568B6.00601BD2.00@d54mta03.raleigh.ibm.com>
Date: Mon, 3 Apr 2000 13:29:43 -0400
Subject: Re: Stable Href's of collections
Another indication these stable hrefs aren't that useful. They may enable
non-versioning clients to do something with versioning meta-data, but it
won't be easy. To get the members of the collection, a client would have to
do a PROPFIND depth 1 on the versioned collection's stable href, examine
all the href's in the result, do a PROPFIND on each one to get the href for
the associated versioned resouce, and parse the URLs to extract the
members.
|------------------------+------------------------>
| | "Tim Ellison/OTT/OTI"|
| | <Tim_Ellison@oti.com>|
| | Sent by: |
| | ietf-dav-versioning-r|
| | equest@w3.org |
| | |
| | 04/03/2000 12:39 PM |
| | |
|------------------------+------------------------>
>------------------------|
| |
| To: |
| ietf-dav-versioning@w|
| 3.org |
| cc: |
| Subject: |
| Stable Href's of |
| collections |
>------------------------|
I seem to remember that we agreed that deep operations on a collection's
stable Href would return responses in terms of stable Hrefs. Makes sense.
Now, assume that I have a stable Href to a collection and would like to
know the names of the collection's members. Previously I'd have used
PROPFIND depth 1 on some property, and got the answer as a "side-effect",
in the <href> tags. However, stable <href>'s cannot be used to extract the
names.
Hmm,
Tim