immutable DAV:merge-predecessors
Geoffrey M. Clemm (geoffrey.clemm@rational.com)
Fri, 3 Dec 1999 07:31:18 -0500
Date: Fri, 3 Dec 1999 07:31:18 -0500
Message-Id: <9912031231.AA11824@tantalum>
From: "Geoffrey M. Clemm" <geoffrey.clemm@rational.com>
To: ietf-dav-versioning@w3.org
Subject: immutable DAV:merge-predecessors
Currently, DAV:merge-predecessors is defined to be a mutable property
of a revision. This means that a client is allowed to change this property
value without checking out the revision.
In the past Jim Amsden has argued that this should be an immutable property,
since it represents a key part of the history of a revision. I believe I
have been the only one arguing that it is useful to be able to change this
aspect of the history to support certain merging scenarios.
I have come to believe that the cost to a server implementation
resulting from requiring the mutablity of DAV:merge-predecessors outweighs
the benefit that results, so I'd like to propose that we follow Jim's
suggestion and make DAV:merge-predecessors be an immutable property.
Anyone disagree?
Cheers,
Geoff