On Mon, 16 Jul 2001, Geoffrey Young wrote:
> hi doug...
>
> what's the game plan for directive handlers in 2.0. I was playing around
> with them in 1.3 quite heavily last week and found myself wondering if it
> wouldn't be cool to have a generic mechanism that you could slip into the
> module record that would allow you to dispense with the Perl*Handler line
> (if you wanted to). doesn't seem that hard if you plan for it, though it'd
> be a kludge to get it into 1.3 it looks like.
>
> not much of a gain, but pretty cool for transparently overriding core
> directives, since you currently need 3 directives (PerlModule, Perl*Handler,
> Directive) to override a C module and have to remember to put the
> Perl*Handler everywhere you will need it.
in 1.x you can already do this:
push @Apache::ReadConfig::Perl*Handler, 'Apache::Foo';
2.0 will probably have something like register_hooks for Perl too.
thing is, i think using directives to configure perl modules is better
than having the modules always be called for a given hook. by forcing
them to be configured in httpd.conf, chances are they will be called less,
rather than always called and return DECLINED if they are not enabled some
other way. the fewer calls into the perl runtime we make, the better the
server will perform.
as for directive handlers, i'd like to avoid having to generate xs code.
but haven't thought about it much yet.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
