You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Geoffrey Young <gy...@laserlink.net> on 2000/04/26 16:57:45 UTC

$r->set_handlers behavior?

good morning...

I'm a bit confused about $r->set_handlers and $r->push_handlers behavior.
Both are listed in the eagle book as being per-request methods, but man
Apache lists them both as server configuration directives.  I think, though,
that I'm seeing set_handlers as persisting with the child and push_handlers
as being per-request.  Personally, I'd rather have set_handlers per-request
as well for situations where I want to add a handler but reorder it with the
existing ones as well...

--Geoff


Re: $r->set_handlers behavior?

Posted by Matt Sergeant <ma...@sergeant.org>.
On Wed, 26 Apr 2000, Geoffrey Young wrote:

> good morning...
> 
> I'm a bit confused about $r->set_handlers and $r->push_handlers behavior.
> Both are listed in the eagle book as being per-request methods, but man
> Apache lists them both as server configuration directives.  I think, though,
> that I'm seeing set_handlers as persisting with the child and push_handlers
> as being per-request.  Personally, I'd rather have set_handlers per-request
> as well for situations where I want to add a handler but reorder it with the
> existing ones as well...

set_handlers is per-request.

-- 
<Matt/>

Fastnet Software Ltd. High Performance Web Specialists
Providing mod_perl, XML, Sybase and Oracle solutions
Email for training and consultancy availability.
http://sergeant.org http://xml.sergeant.org


Re: $r->set_handlers behavior?

Posted by Doug MacEachern <do...@covalent.net>.
On Wed, 26 Apr 2000, Geoffrey Young wrote:

> good morning...
> 
> I'm a bit confused about $r->set_handlers and $r->push_handlers behavior.
> Both are listed in the eagle book as being per-request methods, but man
> Apache lists them both as server configuration directives.  I think, though,
> that I'm seeing set_handlers as persisting with the child and push_handlers
> as being per-request.  Personally, I'd rather have set_handlers per-request
> as well for situations where I want to add a handler but reorder it with the
> existing ones as well...

the {get,set}_handlers patch posted earlier should fix this behavior, can
you confirm?  push_handlers() should probably also be implemented in terms
of r->per_request_config, rather than %Apache::PerlStackedHandlers.