At 18:06 -0800 11/12/03, Stas Bekman wrote:
Geoffrey Young wrote:
for the <Perl> stuff I was talking about, I believe so. however, for directive handlers it does not, so we'd probably need to tweak the interface a bit.
And not for <Perl>, because a random code can be run there in random packages.
But you could document that only the "real" config bits would be available later and anything else lost (unless re-required later). And copy the config bits in a Storable / Data::Dumper format between the interpreters. This is not too dissimilar to what forks.pm does for shared variables and Thread::Tie does.
Even we did enforce that, we still have things like PerlLoadModule which extend the config directives dictionary.
>> for the <Perl> stuff I was talking about, I believe so. however, for >> directive handlers it does not, so we'd probably need to tweak the >> interface a bit. >> but the idea, I guess, is that mod_perl would (eventually) know what >> data is required to be copied, so long as we had a way to do it. > > > Wouldn't Storable or Data::Dumper be able to do such a thing? At the > end of config, dump the pertinent bits to memory (or possibly even a > file), and then read them back in the other interpreter?
I'm not sure as those bits include references to internal C structs.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
