apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject Re: Does mod_perl/mod_??? need a hook called when a request/conn leaves the original worker thread?
Date Mon, 18 Nov 2013 17:29:42 GMT

On Nov 18, 2013, at 12:15 PM, Eric Covener <covener@gmail.com> wrote:

> On Mon, Nov 18, 2013 at 10:58 AM, Jeff Trawick <trawick@gmail.com> wrote:
>> For the mod_perl crash with Event that I posted at the URL below, I would
>> suspect that there's some affinity with the original worker thread.  Can
>> anyone in mod_perl land confirm?
>> 
>> http://mail-archives.apache.org/mod_mbox/perl-dev/201311.mbox/%3CCAKUrXK6C3R_F3NdA%2BJUGYOqppvnoQJLTGQ9%2BA916vuMb0g9dig%40mail.gmail.com%3E
>> 
>> I'm also aware of a third-party diagnostic module that could use a hint, and
>> in general I wonder if anyone knows of specific interface requirements that
>> would need to be provided by a new hook for indicating when a connection or
>> request leaves the original thread or is handled by a new one.
> 
> I can't see any need for more than request_rec on both ends.
> 

mod_spdy uses a fake conn_rec, well, more like a sub-conn_rec
ala a subrequest, which is also sometimes called a slave
connection... I'm thinking that maybe having such an entity
here would be best, long term.
Mime
View raw message