Stas Bekman wrote: > > I'm not talking about mod_perl internals, just talking about amputating a > chunk of the Optree from one interpreter and replanting it into another > interpreter (not perl_cloned one).
You need to explain to me what those interpreters are. IIUC from your remark below the first one is in the root httpd process to parse the config file ; the other ones are in the child httpd processes to process requests ? And you want to slim down the first one ? What are the CV root and CV start of those interpreters ? Why do you want to move CVs from the first one to the later ones ? Just removing them from the first one is not enough ? > I'm not sure whether this is possible at > all. I really want some sort of Storable::freeze, so I can save a CV and all > the related SVs and then resurrect them with ::thaw in another interpreter. The relative SVs ? did you mean the whole contents of stashes and lexical pads ? > To repeat, the problem we have is that we start perl early to do config > parsing (.e.g code run in <Perl> sections) and we really want to kill that > perl when it finished dealing with config, but we need the perl data it > generated to be resurrected in the perl that will process the requests. The whole data+cv moving is theoretically possible but I'm not convinced there will be a significant performance gain. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
