Re: How to create configurations
Jim Whitehead (ejw@ics.uci.edu)
Tue, 6 Apr 1999 18:12:53 -0700
From: Jim Whitehead <ejw@ics.uci.edu>
To: "Geoffrey M. Clemm" <gclemm@tantalum.atria.com>
Cc: ietf-dav-versioning@w3.org
Date: Tue, 6 Apr 1999 18:12:53 -0700
Message-ID: <004c01be8093$c2fd98a0$d115c380@ics.uci.edu>
In-Reply-To: <9904060426.AA27526@tantalum>
Subject: RE: How to create configurations
> I believe there is a way to address JimW's concerns while still
> satisfying JimA's requirements that a snapshot be "usable" in
> a revision-selection-rule (which provides mappings from user-URL's
> to revision-URL's).
If we introduce the notion of a base URL for a configuration managed space,
then the RSRs could be relative to this base URL.
> In particular, we could introduce a DAV:versioned-collection attribute
> for a snapshot. This says that this is a snapshot of *that* versioned
> collection. In this case, all user-URL's of the DAV:scope of the
> snapshot will be *relative* URL's, and only mappings of parent
> collections up to the DAV:versioned-collection will be added to the
> snapshot.
I'm not totally following this. In my mind, there is a base URL for the
entire configuration, not for each collection.
Another scenario driving this kind of (re-host the root collection)
capability is this:
Project Z is normally developed in the following URL tree:
http://www.widgets.com/development/project-z/
Now, suppose the software QA team always works on the project which is in a
different part of the namespace (they could work in /development/project-z/,
but to emphasize the fact its a testing configuration, they work via a
different URL base) they also want to be able to work on this project via
another set of URLs:
http://www.widgets.com/testing/project-z/
Perhaps this part of the namespace has been hard-wired to always use a
workspace with an RSR which selects the "SQA" label.
If you buy into this scenario, then it would be nice to access the project
via multiple base URIs.
- Jim