On Fri, 29 Jun 2001, Stas Bekman wrote:
> I'm going through the files in pod, doing some add-ons from what
> I've learned so far and some minor cleanups. I've a few questions though:
>
>
> modperl_design.pod:
> -----------------------
>
> =head1 Interpreter Management
>
> =item PerlInterpMax
>
> How fast mod_perl responds to the peaks loads when there is a sudden
> demand for a bigger interpreters pool, assuming that
> PerlInterpMaxSpare is set to a low number.
'how fast' will depend on how much code you have compiled in the parent,
and how powerful your machine is. i've not done any measurements.
> BuildOptions::parse_file:
> -----------------------
>
> my @files = map { $_ . 'makepl_args.mod_perl2' }
> qw(./ ../ ./. ../.), "$ENV{HOME}/.";
>
> I think to be really consistent we should do:
>
> my @files = map { $_ . 'makepl_args.mod_perl2' }
> map { ("$_/","$_/.") } qw(. ..), $ENV{HOME};
>
> so we have 6 different locations. it also reads easier :) I know that
> it's probably a bad idea to have makepl_args.mod_perl2 without leading
> '.' under your ~, but just to be consistent. Or may be we should have
> only the files starting with '.'? Just wondering.
i guess ~/makepl_args.mod_perl2 would be ok, but i think that's what i was
trying to avoid originally.
> modperl_dev.pod:
> -----------------------
> =head2 PerlOptions Directive
>
> Is the option called 'Enabled' or 'Enable'? the item says 'Enabled'
> but the example following it uses 'PerlOptions -Enable'
Enabled, i think, try it and see :)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
