RE: Mutable Versions (was: re-use of version URL's)

> Will do, but remember, the whole point of a protocol is to provide
> interoperability.  If you can't count on something being true, an
> interoperable client just has to assume it's not true.  If you can't
> count on a version URL identifying the same content and dead
> properties,
> then you just can't do any of those things that depend on being able
> to count on that.

I believe the requirements for code repositories and the requirements
for document repositories are in some sense incompatible.  Thus, the
client can't count on certain things being true for both kinds of
repositories.

We may need:
 - "type A" where the client can count on versions being immutable and
version URLs being non-reusable
 - "type B" where the client can count on versions being mutable and
version URLs being readable.

I agree the client needs to be able to count on certain behaviour, but
it will have to be a different kind of behaviour depending on what kind
of server it is talking to.  Otherwise the needs of document-versioning
servers will NOT be met by the versioning draft.

lisa

Received on Friday, 5 January 2001 13:50:04 UTC