Next message: Eric Sedlar: "Re: DAV:revision-resourcetype"
Message-ID: <011a01bf63c8$19292880$9a114498@us.oracle.com>
From: "Eric Sedlar" <esedlar@us.oracle.com>
To: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>, <ietf-dav-versioning@w3.org>
Date: Thu, 20 Jan 2000 20:29:25 -0800
Subject: Re: "stable" href's
I've been thinking about the idea of a "fixed" binding within a collection
(a boolean property associated with a link) for caching purposes. Does it
really have to be an entire URL?
--Eric
----- Original Message -----
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: <ietf-dav-versioning@w3.org>
Sent: Thursday, January 20, 2000 8:02 PM
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
>
>