Doug MacEachern wrote:
well, I don't know how difficult it would be, but couldn't there be a separate interpreter for just parsing httpd.conf? I've actually wanted this kind of thing in 1.3 so that I could have both <Perl> sections _and_ lightweight httpd processes using the same server.On Thu, 19 Dec 2002, Stas Bekman wrote:We need to start the interpreter early only to be able to feed the configuration directives (PerlLoadModule and <Perl>). If there was a way to start one interpreter to do the config processing and then somehow start mod_perl normally after the config is over. I need to think some more about it.
first problem: requires ithreads (not acceptable). also, it is likely PerlLoadModule and/or <Perl> will require some of the other config (e.g. PerlSwitches). trickiest part, merging data that was fed from one interpreter to another.
I bet it's possible to get that in 2.0 by just not having a request-time interpreter pool (however that works :) but if there were a separate interpreter used during startup then you wouldn't have to worry about config ordering or passing stuff around - once the config was parsed a new parent interpreter could be spawned with all the proper switches, then that could be used for cloning, code sharing, and whatever.
just some speculating and hand-waving, really :)
--Geoff
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
