Geoffrey Young wrote: [...]
Meaning that you need to document that one needs to do:
PerlLoadModule Foo
which is just as well, could be documented as:
PerlStartNow PerlModule Foo
especially if we are going to add PerlStartNow anyway (are we?).
well, something about that strikes me as dangerous. PerlStartNow has no clear utility. that is, everyone knows what <Perl> sections do, and hopefully we could explain that PerlLoadModule would be for modules that need to run init code. but PerlStartNow is kind of floating in the aether - starting the interpreter on demand has no clear benefit or activity associated with it.
What do you mean it has no clear utility, you've just heard John complaining on the users list that 'apachectl configtest' wasn't invoking mod_perl setup. Unless you think that suggesting to use the <perl> section hack is the best we can come up with.
The only solution I could think of is to add a some hook into config that will check whether we are running under configtest and will force the perl startup at the end of config if it's not running already. These new query status thingies added in 2.0.49 (?) for the starting/restarting may need to be extended to tell us when a 'configtest' is running.
But I
don't have any hard preferences. All I was saying is that if you remove
the magickness of PerlLoadModule with regards to add_module, then the
only remaining difference between PerlModule and PerlLoadModule is that
the latter starts perl.
that's true, except that we can document it in terms of using it for modules that need to interact with config-time activities, such as loading directives into the server before other modules (like mod_authn_basic) get the chance to start.
I guess so. In which case the mnemonics of this directive's name are now not as clear.
And you can't really ensure that a user won't invoke your module via PerlModule.
I had thought about creating some kind of flag (local %ENV or package variable) that would act as a flag in those circumstances. so a module could
die unless $Apache::Module::IsPerlLoadModule;
or something. I admit, it's a stretch, but some mechanism would be nice.
that's wacky. That's why we may need to change the name of that directive, so there will be no confusion.
Sure. I don't think we have any remaining disagreements here.
whew! :)
ok, I'll start working up a patch that will take directive handlers to the next level. keep the ideas coming and we'll get something together that's spiffy :)
I hope we aren't going to piss off too many folks with these late changes...
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
