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.
As far as I can tell, these are the broad things that need to be done:
*Make all mod_perl functions reentrant
*Remove assumptions about the process model
*Remove request stages that may not exist any more (perl child init
handler)
*Make sure that all storage is being done within the request or
connection record (needed because stage X might not have access to the
same local storage as stage A).
*Debug :)
optionally:
*Make mod_perl use APR.
Also there is the additional headache of combing through the Apache::
classes fixing everything that isn't safe, like dependence on global
storage.
I'm assuming that Perl itself is reentrant, since it has been embedded
in multithreaded environments before (IIS). Hopefully someone can
comment on that.
Discuss!
--
Jeffrey W. Baker * [EMAIL PROTECTED]
Critical Path, Inc. * we handle the world's email * www.cp.net
415.808.8807
