John Peacock wrote:
>> Also, we should not be assuming that server configuration comes in the
>> form of a repository config file. Personally, I think all
>> server-to-client configuration goals can be accomplished by adding new
>> directory properties.
>
>
> That's the other option I originally discussed in my #3, but it means
> that each and every directory in the WC must contain a duplicate of the
> available server config data. We aren't usually talking about a lot of
> data, but it is a consideration. It's more of a problem with inherited
> properties (this time assuming that those are associated with directory
> properties).
Actually, it occurred to me that we could have both distributed directory
properties _and_ centralized storage. This gets deeper into implementation than
we should be when discussing design, but if we mark the WC admin files such that
"this directory has additional properties" and then /store/ the shared
properties in the .subversion directory, we get the best of both worlds. The
directories can share the single set of server-mediated config files, and in the
shared WC case, the client code can "know" that it needs to contact the server
to get the server config files when they are not already present in .subversion,
yet are flagged in the WC.
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Apr 30 12:34:01 2005