So, what I believe would help this is to be able to override the DESTROY method for existing objects without changing the source -- essentially, prevent them from running DESTROY, so that they don't flush to disk without my explicit approval.
Ok, so what happened when you tried that? There isn't anything stopping you from overriding the DESTROY method using somethin like use CGI::Session; sub CGI::Session::DESTROY { }. Of course a better solution would be to switch to something that is intended to work with mod_perl, such as Apache::Session.
| We're not surrounded, we're in a target-rich environment! |
|---|
In reply to Re: Judiciously avoiding DESTROY method for CGI::Session clobber prevention
by jasonk
in thread Judiciously avoiding DESTROY method for CGI::Session clobber prevention
by rlucas
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |