"stable" href's

From: Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Date: Thu, Jan 20 2000

  • Next message: Geoffrey M. Clemm: "DAV:resourceid vs. DAV:versioned-resource-id"

    Date: Thu, 20 Jan 2000 23:02:22 -0500
    Message-Id: <10001210402.AA26144@tantalum>
    From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
    To: ietf-dav-versioning@w3.org
    Subject: "stable" href's
    
    
    After thinking for a while about Neil's question about whether a
    MOVE can be applied to a revision, etc., I now believe that it would
    be worthwhile for us to define which properties contain "stable"
    URL's, i.e. URL's allocated by the server that cannot be modified
    by a client with a MOVE request.
    
    Unless anyone objects, I propose to make a pass through the protocol
    identifying those properties which I believe identify stable hrefs.
    
    The value to a client is that it can cache these names with the
    guarantee that another client cannot MOVE them somewhere else.  A
    server can of course chose (or be forced) to break these bindings, but
    there's nothing we can do about that.
    
    Comments?
    
    Cheers,
    Geoff