We basically want to run our scripts under PerlRun with PerlRunOnce Off.
The issue is that because we are a little short handed, and we have many
many many CGIs, any process of cleaning stuff up (maybe 1% has use strict)
would be a long and lengthy one.
PerlRun already flushes everything, but from my understanding of it,
with PerlRunOnce Off mod_perl won't flush the packages that were loaded by
the CGIs. It works fine with PerlRunOnce On, but we want the performance
boost offered by turning it off.
Again, for the reason offered in the first paragraph, we don't want to be
cutting and pasting code to flush variables in *every* module we have,
because we really have a lot.
Because of this we are trying to get the best speed and then distribute
the code maintenance over a long period of time.
Andrew Chen
Intern, Architecture
[EMAIL PROTECTED]
206-219-8445
The Cobalt Group, Inc.
On Thu, 13 Jul 2000, Perrin Harkins wrote:
> On Thu, 13 Jul 2000, Andrew Chen wrote:
>
> > The second strategy is to get mod_perl to compromise between the effects
> > of PerlRunOnce On and PerlRunOnce Off. Is there an easy for for PerlRun to
> > flush everything (including packages) that wasn't preloaded in the
> > startup.pl file? That would be a compromise between killing the child
> > everytime and keeping all the packages around.
>
> It already flushes everything defined within your script. If you want to
> flush things defined in other packages as well, you could copy the (fairly
> simple) code from PerlRun that does this and apply it to other packages.
>
> Before you do this though, consider whether or not you really need to. If
> you're using things from CPAN or that you've written as actual modules
> with their own packages and "use strict" on, you shouldn't need to flush
> them.
>
> - Perrin
>
