On Thu, 2006-04-27 at 00:10 +0200, Lionel MARTIN wrote:
> I can't understand how it could change using a startup.pl file? After all,
> doing a PerlRequire startup.pl is just a way to incoporate code in the main
> flow, isn't it?

Historically, we have sometimes had bugs with this that caused
PerlModule to load code more than once, when use() would not.

> Anyway, I gave it a try, and it gave exactly the same results


> I'm really sceptical (and probably lost) with what you're saying here.
> First of all, from the MP docs itself
> (http://perl.apache.org/docs/2.0/user...hreads_Support),
> I can read that:
> ****************
> Rather than create a PerlInterperter per-thread by default, mod_perl creates
> a pool of interpreters. The pool mechanism helps cut down memory usage a
> great deal. As already mentioned, the syntax tree is shared between all
> cloned interpreters.
> ****************

Liz explains it better than I do:

> I really would love to understand how sharing is working, and what's exactly
> shared (or perhaps have the confirmation that nothing is shared under winnt
> MPMs...?)

I don't know anything about copy-on-write on Win32, but it's mostly
irrelevant once you start using Perl threads anyway. They don't get any
advantage from copy-on-write.

> I think that I should better try with LAMP as well, but to be honest, I have
> never tried to install Linux.

It's easy to install. The hard part is learning how to use a new OS
with new tools. There is an awful lot of help available these days

- Perrin