Re: VirtualHost + PerlSetVar
> OK, we have to do it ourselves, which is easy (.e.g with the patchsorry, I'm a bit late catching up. but yes, I'm very much against doing
> below). The problem is this: all vhosts inherit PerlPostConfigHandler
> from the main server and run it. They all inherit the PerlSetVar as
> well. I'm not sure this is the wanted behavior. I suppose this is why
> Apache doesn't do it for each vhost. Comments?
> Index: src/modules/perl/mod_perl.c
this in core - it make the Perl API very different from the C API. the way
you've done it in the current startup.pm is the way that core modules (such
as mod_rewrite) do it, so I'd rather stick to that as the paradigm.
but you probably already came to the same conclusion - nice work getting the
server-loop integrated into the test suite :)
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html