That's odd. I thought I remembered reading up about discouraging the use
of the CGI module in optimising modperl.
The rationale (if I remembered right) is that CGI depends on the %ENV,
which populating it for every call is an effort. The recommended way is
to turn of SetupEnv, and grab as much stuff from Apache2::RequestRec as
possible.
Perrin Harkins wrote:
Foo Ji-Haw wrote:
So what you are saying, is that it is generally fine in a production
environment to continue using CGI::Cookie?
Yes.
But it does not infer that using CGI is just as well right?
The CGI.pm module? That's fine too.
- Perrin
