Rafael Garcia-Suarez wrote:
Geoffrey Young wrote:
the problem with this, though, is that we don't really want a clean interpreter, we want an _almost_ clean one - one with only the data we know is important (like the globals set within the <Perl> section). so, if we could copy the relevant data from the first interpreter and insert it into the one we're about to clone for the request, we'd have the best situation possible - minimal data in the parent interpreter.
Problem : how to separate the relevant data from the irrelevant one ? Does it live in a particular package ?
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 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.
That's why I was talking about diffing the Optree before and after the config phase.
I imagine it's possible to e.g. add an attribute on stashes that say
"don't clone me". And implement a function "require_for_this_interpreter_only $module"
in an XS module.
which goes back to the problem of being able to do it dynamically, i.e. sort of doing the diff I'm talking about above.
__________________________________________________________________ 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]
