hi
unless I'm missing something, all hooks are always enabled and EVERYTHING=1 hasn't been implemented yet.
we probably need to support EVERYTHING=1 and all the other associated (un)hooking stuff in the build environment.
I don't think there is a need for that. You can enable/disable hooks dynamically from the config file:
http://perl.apache.org/docs/2.0/user/config/config.html#C_Perl_Handler_
in addition to that, I'd like to add support for hook position. that is, make it possible to have, say, content as APR_HOOK_FIRST but translation as APR_HOOK_LAST.
What API were you thinking of?
both of these require changes to modperl_hooks.c, which is autogenerated. my initial thought was to share a global ($ModPerl::BuildOptions::options ?) between ModPerl::BuildOptions and ModPerl::Code, but I wasn't sure about that.
thoughts?
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
__________________________________________________________________ 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]
