that is not quite mod_perl compliant
If a third-party module uses global variables internally that causes
persistence of the data under mod_perl, is there a fix.
You can manually clear them in a cleanup handler. If they're in a
separate package, you can clear the whole namespace of the package
To the list of mod_perl experts,
If a third-party module uses global variables internally that causes persistence of
the data under mod_perl, is there a fix. This particular module has a lot of
dependencies on other modules, so fixing the third-party stuff may not be practical.
It really
If a third-party module uses global variables internally that causes
persistence of the data under mod_perl, is there a fix.
You can manually clear them in a cleanup handler. If they're in a
separate package, you can clear the whole namespace of the package. Take
a look at the code for this
