[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Multiple access filess when using SVNParentPath

From: Michael Sinz <Michael.Sinz_at_sinz.org>
Date: 2005-12-02 03:26:12 CET

Max Bowsher wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ben Collins-Sussman wrote:
>
>>Actually, if there's enough inertia to add a new feature here, I'd
>>much rather see the authz-policy file gain the ability to "#include"
>>sub-files, much like the way httpd.conf is able to do. (Somebody here
>>already suggested that.)
>>
>>In addition to solving the original poster's problem, it will add
>>general flexibility.
>
>
> It doesn't solve the OP's problem, unless you have a complicated include
> system which doesn't just include, but also allows you to restrict
> included files to affect only a specific repository.
>
> In view of this, I don't really see what benefit an include capability
> gives.

I was the one that initially brought up the include option - mainly as a
way to split the file without having to do as much of a change. I did not
intend the include mechanism to enforce anything - just to enable the
external enforcement of "file a for repository a"

I would much rather have the system natively understand this for various
reasons...

> Note that the servers re-load and re-parse the config file for every
> connection - in the case of HTTP, this is a lot, and having to do this
> for multiple files could get quite unpleasant.

This is where having the auth file per repository would help - only the
auth file for the path/repository being requested would need to be read
in any one request. This could be a significant savings (albeit reasonable
in-core caching of the last read with timestamp checks would provide much
of the same benefit)

> Then, there is the difficultly of defining how to merge conflicting
> statements between multiple files.
>
> At the moment, I don't understand any use-cases for include.

Like I said, the rules would be to treat it just as a single file (other
than being able to have multiple groups sections - maybe)

Anyway, I would much rather have the per-repository authentication file.
I believe it would be able to provide the biggest benefits.

-- 
Michael Sinz                     Technology and Engineering Director/Consultant
"Starting Startups"                                mailto:michael.sinz@sinz.org
My place on the web                            http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Dec 2 03:27:30 2005

This is an archived mail posted to the Subversion Dev mailing list.