Next message: Clemm, Geoff: "RE: Extending Target-Selector"
From: Tim_Ellison@oti.com (Tim Ellison OTT)
To: ietf-dav-versioning@w3.org ('Delta V')
Message-ID: <2000Mar02.091700.1250.1495048@otismtp.ott.oti.com>
Date: Thu, 02 Mar 2000 09:21:49 -0500
Subject: RE: Extending Target-Selector
<geoff>
Depth infinity operations in the stable namespace would return stable URL's
and depth infinity operations in the user namespace would return user
namespace URL's.
I assume you were talking about depth infinity operations in the user
namespace, so I agree with your assumption that they are user URL's in the
response.
</geoff>
Do we still have target selector 'meta' to denote stable URLs?
I don't recall seeing it in the doc.
<geoff>
As for Target-Selector, I believe our last agreement was to have two
headers, Revision-Selector and Workspace. The Workspace header affects
version selection for any resource encountered while processing the request.
The Revision-Selector header only applies to the resource identified by the
Request-URL, and if that resource is a working resource, revision, or
versioned resource, it causes the target of the request to be the specified
revision instead.
</geoff>
Really, the target selector would choose a revision in preference to a
working resource!
<geoff>
So with depth infinity requests, the Revision-Selector header only applies
to the Request-URL, and only the Workspace header applies to all the
resources encountered by the request.
</geoff>