Next message: Tim Ellison OTT: "RE: "stable" href's"
Message-ID: <65B141FB11CCD211825700A0C9D609BC01879916@chef.lex.rational.com>
From: "Vasta, John" <jvasta@Rational.Com>
To: ietf-dav-versioning@w3.org
Date: Wed, 26 Jan 2000 12:55:05 -0500
Subject: RE: "stable" href's
But how would a client know whether any random URL returned by a server
corresponds with something the client has control over, vs. something that
the server controls? Simply declaring which properties contain
server-controlled URLs seems like a useful piece of information.
John
> -----Original Message-----
> From: jamsden@us.ibm.com [mailto:jamsden@us.ibm.com]
> Sent: Wednesday, January 26, 2000 11:31 AM
> To: ietf-dav-versioning@w3.org
> Subject: Re: "stable" href's
>
>
>
>
> Geoff,
> This feels a little like exposing server implementation
> details to clients.
> Some servers may need to move these URLs around for one
> reason or another.
> So clients should only rely on the URL bindings they made and
> shouldn't be
> messing with server URLs. I know we've said that there will
> be a stable URL
> for each resource for versioning unaware clients, but I don't
> think those
> URLs will be useful, especially to versioning unarare clients
> because they
> won't resemble anything meaningful.
>
>
>
>
>
>
> "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>@w3.org on 01/20/2000
> 11:02:22 PM
>
> Sent by: ietf-dav-versioning-request@w3.org
>
>
> To: ietf-dav-versioning@w3.org
> cc:
>
> 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
>
>
>
>