Re: Versioning and locking
jamsden@us.ibm.com
Sun, 23 May 1999 08:12:02 -0400
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <8525677A.00436644.00@d54mta03.raleigh.ibm.com>
Date: Sun, 23 May 1999 08:12:02 -0400
Subject: Re: Versioning and locking
Geoff says:
My concern was that a non-versioning-aware client would issue a lock (just
wanting
that resource to not change), but if that resource was a versioned-resource that
selects
a revision,this lock would have a "create no successor" semantics, which is a
much
stronger statement than the non-versioning-aware client intended to make (it
just
didn't want the resource that it sees at that URL to change).
A non-versioning aware client locking a versioned resource would prevent anyone
else from making any change to any revision of that versioned resource. But from
the point of view of that client, that's what he wanted.
I don't think we should get too hung up on supporting non-versioning aware
clients. As long as we support access and minimal authoring, I think we will
have met the spirit of down-level support. Allowing non-versioning aware clients
to do versioning semantics through round about means will just add complexity to
the protocol without making such access consistent with down-level clients.