Sinclair, Alan (CORP, GEAccess) wrote:
All,
Starting to strike the first blows with Apache 2.0. I am now wondering about
thread safety with mod_perl 2. Will mod_perl support a threaded MPM Apache
config ?
Why using the future tense, it does support the threaded mpm pretty much
from the very
Well, from the looks of the cvs commits, doug seems to be compiling
mod_perl under apache 2.0 quite regularly :) With the complete rewrite
there's been plenty of work to do.
The word on it is here:
http://perl.apache.org/~dougm/modperl_2.0.html
its still in heavy development by doug - i would
On Wed, 3 Nov 1999, Jeffrey Baker wrote:
There was a short discussion a while ago about getting mod_perl working
with Apache 2.0. Since Apache 2.0 can actually be built and run on a
few platforms now, I think it is worth taking a lot at this for real.
I started to fiddle with 5.005_63 and
I'm assuming that Perl itself is reentrant, since it has been embedded
in multithreaded environments before (IIS). Hopefully someone can
comment on that.
Perl 5.005 has experimetal thread support, Perl 5.006 might be stable
enought to really use it.
What ActiveState has done for IIS, is to
"C. Jon Larsen" wrote:
One of the main reasons I use mod_perl is because of the pre-fork caching
I can do in the parent that the children can share cheaply. I take huge
data structures and assemble them in ram as read-only databases (read
hash tables) that are much faster and simpler to
Perl threads have nothing to do with OS level threads. They aren't
native; they're part of the language itself and don't depend or rely
on POSIX threads, native threads, or other such things. In
particular, Perl threading doesn't mean that Perl is thread safe.
Yes, Perl threads are not
Matt Sergeant wrote:
On Thu, 04 Nov 1999, Jeffrey Baker wrote:
I'm assuming that Perl itself is reentrant, since it has been embedded
in multithreaded environments before (IIS). Hopefully someone can
comment on that.
This work was based on PERL_OBJECT support, which is currently only
