Re: WeDAV Versioning Summary
Geoffrey M. Clemm (gclemm@tantalum.atria.com)
Wed, 14 Apr 1999 17:52:09 -0400
Date: Wed, 14 Apr 1999 17:52:09 -0400
Message-Id: <9904142152.AA06981@tantalum>
From: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
To: sv@crystaliz.com
Cc: jamsden@us.ibm.com, ietf-dav-versioning@w3.org
In-Reply-To: <00f701be8608$3a3d2a60$e6ea7392@honeybee> (sv@crystaliz.com)
Subject: Re: WeDAV Versioning Summary
From: "Sankar Virdhagriswaran" <sv@crystaliz.com>
> Simple parallel development can be accomplished by using the null
activity.
The use of the term 'null activity' out of the blue. Might be wise to refer
to what this 'null activitiy' is.
We need to update this section to reflect the "current-label"
semantics. For example:
****
Parallel development is available at level one through the use of a
"current-label" for a workspace. The current label is
automatically moved to any new revision that is checked-in to that
workspace. Two workspaces with different "current-labels" can work
in parallel on the same versioned-resource, and then merging can be
performed by adding both labels to the revision selection rule of
the workspace performing the merges.
A level one workspace would then by default have a single "label=default"
revision-selection-rule property and a "current-label default" property.
***
Then the concept of a "null activity" can be eliminated. There is the
notion that a level two server can behind the scenes maintain
activities for a workspace that is using a current-label, but that's
not something a level one client needs to know about (either at the
protocol or in the version model).
> A server may allow many checkouts of the same revision using the null
> activity. Merge is not supported for the null activity, client
applications
> are responsible for integrating the changes.
But, the above three sentances don't say how 'simple parallel development'
can be accomplished with 'null activity'.
Basically, it can't (:-).
Cheers,
Geoff