http://perl.apache.org/docs/2.0/use...Threads_Support

Regards,
Nicolas

[ Post a follow-up to this message ]

On Mon, 13 Feb 2006, Nicolas Lehuen wrote:

> http://perl.apache.org/docs/2.0/use...Threads_Support

Which part of it - the pool of interpreters? Are they doing it out of
necessity, i.e. there is no way to run multiple threads in PERL like we do
in Python because of Python's GIL?

Grisha

[ Post a follow-up to this message ]

It seems that bu dfdefault PERL is not thread safe, and that they have
to jump through all those hoops to ensure thread safety. There is no
real lesson for mod_python, I just wanted to know how they solved this
rather difficult problem.

Not instantiating one interpreter per name per thread and using an
interpreter pool may be an interesting optimisation, though. But I
guess it's a rather complicated one.

Regards,
Nicolas

2006/2/13, Gregory (Grisha) Trubetskoy <grisha@apache.org>:
>
> On Mon, 13 Feb 2006, Nicolas Lehuen wrote:
> 
t[vbcol=seagreen]
>
> Which part of it - the pool of interpreters? Are they doing it out of
> necessity, i.e. there is no way to run multiple threads in PERL like we d=
o
> in Python because of Python's GIL?
>
> Grisha
>

[ Post a follow-up to this message ]