On Mon, 3 Jun 2002, Doug MacEachern wrote:
> On Mon, 3 Jun 2002, Stas Bekman wrote:
>
> > Does this mean that any END blocks registered during a request handler,
> > will be run at the end of it and not at the shutdown? If not where do
> > they go if PL_endav is getting reset to its pre-reque
On Mon, 3 Jun 2002, Stas Bekman wrote:
> Does this mean that any END blocks registered during a request handler,
> will be run at the end of it and not at the shutdown? If not where do
> they go if PL_endav is getting reset to its pre-request value.
only if SetHandler is perl-script, PL_endav
> > MP_perl_global_entries[] = {
> > {"END",MP_GLOBAL_OFFSET(end),MP_GLOBAL_AVCV}, /* END
> */
> >
> > What's global END()? I thought END always belong to some namespace.
>
> nope. PL_endav is global.
Does this mean that any END blocks registered during a request handler,
On Sun, 2 Jun 2002, Stas Bekman wrote:
> Does this also mean that with 'SetHandler modperl' the coder should be
> extremely careful not to pollute these globals and therefore we should
> add a warning in the relevant docs?
yes.
---
On Sun, 2 Jun 2002, Stas Bekman wrote:
> MP_perl_global_entries[] = {
> {"END",MP_GLOBAL_OFFSET(end),MP_GLOBAL_AVCV}, /* END */
>
> What's global END()? I thought END always belong to some namespace.
nope. PL_endav is global.
> {"ENV",MP_GLOBAL_OFFSET(env),MP_GLOBA
Stas Bekman wrote:
> Doug MacEachern wrote:
>
> There is one item of your reply I need more details about:
>
>>> SetHandler perl-script
>>
> ...
>
>>> implies:
>>
> ...
>
>>> * there are a few other things that happen in this function, what are
>>>they?
>>
>>
>>
>> modperl_perl_global_re
Doug MacEachern wrote:
There is one item of your reply I need more details about:
>> SetHandler perl-script
...
>>implies:
...
>>* there are a few other things that happen in this function, what are
>>they?
>
>
> modperl_perl_global_request{save,restore} does something like local() for
David Jacobs wrote:
> I've had trouble benchmarking some of my mod_perl scripts on my desktop.
> The http_load tool we usually use (all under RedHat) works fine with
> static pages or CGI, but when I use it on mod_perl scripts I get a "byte
> count wrong" error. This could be because of somethi
I've had trouble benchmarking some of my mod_perl scripts on my desktop.
The http_load tool we usually use (all under RedHat) works fine with
static pages or CGI, but when I use it on mod_perl scripts I get a "byte
count wrong" error. This could be because of something unexpected in the
header
"perl-script" is exactly what you've in 1.0
"modperl" is the bare bones. See the tests in t/ that run under
"modperl" and you will understand what's the difference.
SOme time in the future I'll run some benchmarks and will post the
results. modperl should be faster than "perl-script".
__
At 00:23 23.05.2002, Issac Goldstand wrote:
>Per Einar Ellefsen wrote:
>
>>At 23:42 22.05.2002, Issac Goldstand wrote:
>>
>>>Doug MacEachern wrote:
>>>
On Thu, 23 May 2002, Stas Bekman wrote:
>We don't have the difference between
> SetHandler perl-script
>and
> SetHand
Per Einar Ellefsen wrote:
> At 23:42 22.05.2002, Issac Goldstand wrote:
>
>> Doug MacEachern wrote:
>>
>>> On Thu, 23 May 2002, Stas Bekman wrote:
>>>
We don't have the difference between
SetHandler perl-script
and
SetHandler modperl
documented.
>>>
>>>
>>> in a nutsh
At 23:56 22.05.2002, Per Einar Ellefsen wrote:
>At 23:42 22.05.2002, Issac Goldstand wrote:
>>Doug MacEachern wrote:
>>
>>>On Thu, 23 May 2002, Stas Bekman wrote:
>>>
We don't have the difference between
SetHandler perl-script
and
SetHandler modperl
documented.
>>>
>>>in
At 23:42 22.05.2002, Issac Goldstand wrote:
>Doug MacEachern wrote:
>
>>On Thu, 23 May 2002, Stas Bekman wrote:
>>
>>>We don't have the difference between
>>> SetHandler perl-script
>>>and
>>> SetHandler modperl
>>>documented.
>>
>>in a nutshell, 'perl-script' does everything it did in 1.x
>>'
Doug MacEachern wrote:
>On Thu, 23 May 2002, Stas Bekman wrote:
>
>>We don't have the difference between
>> SetHandler perl-script
>>and
>> SetHandler modperl
>>documented.
>>
>
>in a nutshell, 'perl-script' does everything it did in 1.x
>'modperl' does nothing special, just the callback.
>
c
On Thu, 23 May 2002, Stas Bekman wrote:
> We don't have the difference between
>SetHandler perl-script
> and
>SetHandler modperl
> documented.
in a nutshell, 'perl-script' does everything it did in 1.x
'modperl' does nothing special, just the callback.
> implies:
>
> * PerlOptions +Glo
> BTW, why modperl_env_request_populate() is called only for perl-script
> handler and not for modperl?
I've figured this one out. That means that if you run under SetHandler
"modperl" there is no way to 'Options +SetupEnv' and "perl-script" is
the only option. I guess this is how it should be
We don't have the difference between
SetHandler perl-script
and
SetHandler modperl
documented.
Source code wise it seems that modperl_response_handler_cgi is what
makes them different. I've started documenting the difference, but I
don't understand everything and need help. Here is the sta
18 matches
Mail list logo
