Perrin Harkins wrote:
On Thu, 2005-10-06 at 11:53 -0400, Jim Albert wrote:
Besides the fact that if I choose
the scripts to run mod_cgi perhaps in a non mod_perl environment,
then
they are all set to go.
This is true with Registry scripts as well.
I thought this was safer than calling CGI::initiliaze_globals
I don't think it is. Guessing at which ones need to be cleared sounds
less safe to me.
I have successfully used the CGI::initialize_globals workaround when
needing to support CGI.pm with subrequests, and I recommend that you use
it if you want to stick with CGI.pm.
Yes, I agree. Especially since I had to move to using CGI.pm via OO
anyway so any changes that CGI.pm makes to those globals just happen
again after me clearing the globals when i I call the CGI::new() method.
I had previously thought best otherwise when I thought I could continue
to use CGI.pm non-OO.
Thanks for bringing that to mind.
Ultimately, you're better off abandoning CGI.pm for something else.
There are alternatives with an identical API if all you need is
parameter parsing.
OK, thanks... I'll check some of them out when I have some more time.
Right now, CGI::initiliaze_globals is the quickest way for me to get my
problem resolved.
Thanks all for confirming my thoughts on this problem.
--
Jim Albert
