> > 2. Leave %Apache::ReadConfig:: alone until right after the config phase > and feed it to Apache::PerlSections in one go > > Problem with this that processing of Apache::ReadConfig (for modules and > code that push into it themselves) will be delayed at the very end and > might break existing things that expects it to be processed at the end > of the <Perl> block that ran... > > I dunno about anybody else, but I prefer solution 2, but what do you > think?
in all the stuff I've done with adding directly to the ReadConfig namespace, I don't _think_ I've ever relied on the exact placement of the directives. so, it _sounds_ ok to me (at the moment :) --Geoff --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
