Re: How to create configurations
Jim Whitehead (ejw@ics.uci.edu)
Mon, 5 Apr 1999 16:21:44 -0700
From: Jim Whitehead <ejw@ics.uci.edu>
To: Versioning <ietf-dav-versioning@w3.org>
Date: Mon, 5 Apr 1999 16:21:44 -0700
Message-ID: <000101be7fbb$12085360$d115c380@ics.uci.edu>
In-Reply-To: <8525674A.0055C37A.00@d54mta03.raleigh.ibm.com>
Subject: RE: How to create configurations
> Adding a resource to a configuration adds the URL of the resource and
> its parent collections recursively up the collection hierarchy to the
> root. The URL must refer to a versioned resource, and the revisions
> selecded for the configuration must be immutable.
Jim,
Thanks for taking the time to write this message about configurations -- it
really helped my understanding a lot.
However, reading through your post, I was struck by the requirement I quoted
above. It seems to me there are many use cases where you don't want to add
the URLs of parent collections all the way to the root.
For example, if I have a Web server set up so my personal working space is:
http://davserver.uci.edu/people/jim/
(where other users are added under /people/)
I wouldn't want to have /people/ added into a configuration of some project
which starts under /jim/. I'm hoping you really meant "to the root of the
project" or something like that, where, if in the example above I was
working on two projects:
http://davserver.uci.edu/people/jim/program1/
http://davserver.uci.edu/people/jim/program2/
(where /program1/ and /program2/ are the root URLs of a hierarchy of Web
resources for source code, design document, requirements, etc.)
In this case, I would want a set of configurations for /program1/ and a set
of configurations for /program2/ (and never the two shall meet).
- Jim