RE: "stable" href's

From: Tim Ellison OTT (Tim_Ellison@oti.com)
Date: Fri, Jan 21 2000

  • Next message: Tim Ellison OTT: "RE: DAV:resourceid vs. DAV:versioned-res"

    From: Tim_Ellison@oti.com (Tim Ellison OTT)
    To: ietf-dav-versioning@w3.org (ietf-dav-versioning)
    Message-ID: <2000Jan21.102031.1250.1452102@otismtp.ott.oti.com>
    Date: Fri, 21 Jan 2000 10:21:12 -0500
    Subject: RE: "stable" href's
    
    
    Good idea.
    
    Tim
     ----------
    >From: Geoffrey M. Clemm
    >To: ietf-dav-versioning
    >Subject: "stable" href's
    >Date: Thursday, January 20, 2000 11:14PM
    >
    >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
    >
    >