|
RE: Using a module that is not quite mod_perl compliant: msg#00233apache.mod-perl
Perrin, Thanks, I should have known that, but I haven't had this problem before. Chuck -----Original Message----- From: perrin@xxxxxxxx [mailto:perrin@xxxxxxxx] Sent: Friday, July 26, 2002 7:48 PM To: Goehring, Chuck Mr., RCI - San Diego Cc: modperl@xxxxxxxxxx Subject: Re: Using a module 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. Take a look at the code for this in Apache::PerlRun. - Perrin |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | [DIGEST] mod_perl digest 2002/07/22: 00233, jgsmith |
|---|---|
| Next by Date: | Re: PerlAccessHandler: 00233, Robert Landrum |
| Previous by Thread: | Re: Using a module that is not quite mod_perl complianti: 00233, perrin |
| Next by Thread: | okay, I give, I'm stumped: 00233, Greg Rumple |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |