Jim Albert wrote: > Lack of response on this tells me: > > 1. Nobody is using ModPerl::PerlRun any longer to run their scripts > under mod_perl. I doubt it.
>From the docs: This module is meant for "Dirty" CGI Perl scripts and The Apache::Registry handler is much faster So new development shouldn't be targetting PerlRun anymore, but Registry. If you are trying to work with a legacy app, then that is more understandable. > 2. There is an alternative to CGI.pm that is mod_perl safe. If there is > a mod_perl safe alternative to CGI.pm for use under ModPerl::PerlRun > scripts for things like retrieving input from QUERY_STRING and working > with cookies, please point me to what you use for this. Have you tried using CGI.pm in an OO fashion to see if it fixes the problem you're having? If that doesn't work, then I'd suggest sticking with your original thought and just do the resetting the globals yourself at the beginning of every request. CGI::_reset_globals(); I don't think your scenario is common enough to get this put into CGI.pm itself since it would slow down everyone else (which is why Lincoln put it into a cleanup handler in the first place, so it's run after the output has been sent to the browser). But you may be able to convince Lincoln to make the method public and documented so that it won't get ripped out from under you some day. -- Michael Peters Developer Plus Three, LP
