Yuriy Syrota wrote:
if I guess correctly, your current problem is that Apache doesn't recognize the extended configuration directives, because PerlModule doesn't run the code that installs these directives, right away. Is that correct?Hello, folks.I performed additional investigation and now can ask the question more accurately. Well, let's start from the beginning. I'm porting AxKit to apache2. AxKit is a mod_perl module which registers itself in apache as a regular module written in C with own configuration directives (there is some C code in the AxKit which do it when mod_perl are loading AxKit). In Apache2 this approach doesn't work because PerlModule directive does nothing at the httpd.conf parsing phase. And
Would <Perl> sections / startup file help?
I can't load this module by LoadModule because AxKit doesn't define @APACHE_MODULE_COMMANDS, AxKit registers itself into Apache. So, now I wonder are there any ways to write such kind of modules under mod_perl2? Do I really should rewrite this part of AxKit under Perl and load it by LoadModule?
__________________________________________________________________ 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]
