On Sunday 23 December 2001 09:38 am, Ryan Bloom wrote: > On Sunday 23 December 2001 06:27 am, Jeff Trawick wrote: > > Greg Ames <[EMAIL PROTECTED]> writes: > > > > > ...are more painful to deal with than you might think, if the user is > > > allowed to code them in any order. > > > > another thing is that the user can code any number of them, possibly > > with different values... swapping items in the tree doesn't > > necessarily deal with that properly while doing stuff in a post-config > > hook wouldn't run into problems (it could just use the setting from > > the last time the directive occurred) > > Yeah, but that can be handled by searching from the end of the list instead > of the front. The problem with doing it in post-config is that it isn't generic > enough. It will work for any directive that is only allowed in the main server > config, but you can't really use it for anything in a different scope. Since > we already know that we need this general ability for some of the auth > directives (see John Sterling's posts about some of the problems with AuthType > and AuthName), I would much rather have a generic function that will > manipulate the tree itself.
I thought of another reason to do this in the tree itself. The point of the config tree is to keep the current config in memory. If you are going to modify the config, you need to modify it in the tree. By doing to work on the tree, you get that for free. Ryan ______________________________________________________________ Ryan Bloom [EMAIL PROTECTED] Covalent Technologies [EMAIL PROTECTED] --------------------------------------------------------------
