Re: target selector again & again
Tim Ellison OTT (Tim_Ellison@oti.com)
Wed, 06 Oct 1999 17:04:16 -0400
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
Message-ID: <1999Oct06.170200.1250.1344207@otismtp.ott.oti.com>
Date: Wed, 06 Oct 1999 17:04:16 -0400
Subject: RE: target selector again & again
<sarge>
So precisely how do you get the revision's URL?
Assuming you normally use the versioned resource's
URL you have to query to discover the revision's URL
(or the history URL and the revision-id). This is not a new
problem, but I don't immediately see how it's done with
the current protocol.
</sarge>
<tpe>
How about this:
1) PROPFIND myresource -> DAV:history-uuid
2) PROPFIND myresource -> DAV:revision-id
3) some random call to find out where in the namespace the server
creates history resources; maybe OPTIONS myresource??
4) the URL is
http://foo.com/<history_place>/<history_uuid>/<revision-id>
Problems:
a) it's three calls to the server to deduce this fundamental
information,
b) step (3) has not ben defined, indeed there are suggestions that the
server should not dictate this information.
</tpe>