RE: Extending Target-Selector

From: Clemm, Geoff (gclemm@Rational.Com)
Date: Wed, Mar 01 2000

  • Next message: Tim Ellison OTT: "Re: Disappearing CHECKINs"

    Message-ID: <65B141FB11CCD211825700A0C9D609BC01D4D73A@chef.lex.rational.com>
    From: "Clemm, Geoff" <gclemm@Rational.Com>
    To: ietf-dav-versioning@w3.org
    Date: Wed, 1 Mar 2000 18:00:43 -0500 
    Subject: RE: Extending Target-Selector
    
    
    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.
    
    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.
    
    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.
    
    Cheers,
    Geoff
    
    -----Original Message-----
    From: Tim_Ellison@oti.com [mailto:Tim_Ellison@oti.com]
    Sent: Wednesday, March 01, 2000 4:05 PM
    To: ietf-dav-versioning@w3.org
    Subject: Extending Target-Selector
    
    
    
    Do we expect depth infinity operations to return stable URLs or 'users' 
    URLs.
    
    For example, PROPFIND depth infinity would be difficult to decode if the 
    URLs were all stable URLs--so I'll assume that they are user URLs in the 
    response.
    
    Now if you extend Target-Selector to be:
         All-But-Leaf-Selector: and
         Leaf-Selector:
    (we can argue about the names :-)
    How do you interpret the results?  Do the deep URLs conform to the same 
    All-But-Leaf-Selector: and Leaf-Selector: selection?  That's confusing since
    
    the request-url used to have a leaf at the end, but in the deep operations 
    it's segments are all 'all-but-leaf' segments.  If the dep URLs don't 
    conform tot he same selection criteria what do they conform to?
    
    Tim