Stas Bekman wrote:
What do you think?
I definetely think we should generate different sequences per child.
Later we may extend this to other phases as well (e.g. prevent
registering Auth handler, from response phase). of course assuming that
we find an efficient way to do that.
I wonder
verUtil->server->push_handlers(PerlChildInitHandler => 'foo');
...
1;
now if the module is loaded at the server startup, it'll register the
callback just fine. If not and it'll be attempted to load after the server
startup, that push_handlers call will fail, s
> -Original Message-
> From: Gerald Richter [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 09, 2001 2:45 PM
> To: Geoffrey Young; [EMAIL PROTECTED]
> Subject: Re: phases...
>
>
> >
> > do all mod_perl hooks correspond to apache hooks?
>
>
>
> do all mod_perl hooks correspond to apache hooks?
more or less..., CleanupHandler isn't quite an Apache Hook, but get's called
when Apache cleans up his request data.
>Do they have to?
>
mod_perl doesn't get control outside of a Apache hooks (and resource
cleanup). The only addtional possib
just a little internals question...
do all mod_perl hooks correspond to apache hooks? Do they have to?
I've always wondered if it would be possible to add an extra pseudo-phase
after content generation - kinda so I could set up different s to
do whatever, then run EVERY request through a proces
