Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-24 Thread David E. Wheeler
On Apr 24, 2008, at 02:20, Torsten Foertsch wrote: Well, I think I can shed some light on that mystery. When you use the "perl-script" handler instead of "modperl" then your C-level response handler is modperl_response_handler_cgi (see src/modules/perl/ mod_perl.c). This function calls modper

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-24 Thread Torsten Foertsch
On Wed 23 Apr 2008, David E. Wheeler wrote: > No subrequest appears at all! So this leads me to conclude one of two   > things. Either > > 1. Internally, mod_perl's TransHandler code triggers the subrequest.   > Why it would, I have no idea, but if there is no TransHandler, that   > code doesn't ex

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread David E. Wheeler
On Apr 23, 2008, at 11:53, David E. Wheeler wrote: I was fiddling with that yesterday, and $r->main seemed to return true every time. But I'll try again. The /101/ request *is* a subrequest? WTF is that coming from? It seems to happen after the AccessHandler finishes, but before the Respo

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread David E. Wheeler
On Apr 23, 2008, at 11:19, David E. Wheeler wrote: On Apr 23, 2008, at 11:16, Torsten Foertsch wrote: I think the /101 request is a subrequest. Do you use path_info? This together with the perl-script handler can cause a subrequest when apache wants to translate PATH_INFO to PATH_INFO_TRANS

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread David E. Wheeler
On Apr 23, 2008, at 11:16, Torsten Foertsch wrote: I think the /101 request is a subrequest. Do you use path_info? This together with the perl-script handler can cause a subrequest when apache wants to translate PATH_INFO to PATH_INFO_TRANSLATED. You can distinguish between a subrequest an

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread David E. Wheeler
On Apr 23, 2008, at 11:09, Geoffrey Young wrote: cleanup handlers are just callbacks run when a memory pool goes out of scope. Oh. And here I thought that they ran when the request completed. your test suggests that the memory pool allocated for the request is going out of scope before the

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread Torsten Foertsch
On Wed 23 Apr 2008, David E. Wheeler wrote: > I'm busy finalizing the port of Bricolage to mod_perl2. In the   > process, I've discovered a bit of weirdness with our TransHandler. For   > certain requests, it seems to execute twice. Under mod_perl1, here's   > an example: > > 75947 Apache=SCALAR(0x

Re: Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread Geoffrey Young
Under mod_perl2, however, the same request looks like this: 75749 Apache2::RequestRec=SCALAR(0x29f3300) TransHandler start for /workflow/profile/desk/101/101/ 75749 Apache2::RequestRec=SCALAR(0x29f3300) TransHandler finish for /workflow/profile/desk/101/101/ 75749 Apache2::RequestRec=SCALAR

Porting Bricolage to mp2: TransHandler Interference

2008-04-23 Thread David E. Wheeler
Howdy, I'm busy finalizing the port of Bricolage to mod_perl2. In the process, I've discovered a bit of weirdness with our TransHandler. For certain requests, it seems to execute twice. Under mod_perl1, here's an example: 75947 Apache=SCALAR(0x295ed70) TransHandler start for /workflow/ p