Take this with a grain of salt because I have a very DEEP bias
against CGI.pm.
Apache::Request is a module that you can get via CPAN. It's
purpose is to emulate the core functionality of CGI.pm, except that it
was written in C and consequently is a) much faster and b) has a much
smaller memory foot print. The ONLY downside to it that I have found (but
I never use this feature, so don't care at all) is that Apache::Request
does not allow you to build HTML. Since I use a template solution, I
don't care AT ALL about the lack of the HTML creation feature.
That being said, because CGI.pm is a bloated piece of code, I
typically rewrite or don't use modules that depend on CGI.pm because of
it's size (and because it's slow). Apache::Request behaves the same as
CGI.pm, but the manual will explain more of that when you install it. ;)
--SC
On Thu, 17 Feb 2000, Louis-David Mitterrand wrote:
> Date: Thu, 17 Feb 2000 14:43:33 +0100
> From: Louis-David Mitterrand <cunctator@apartia.ch>
> Reply-To: ldm@aparima.com
> To: Sean Chittenden <sean@serverninjas.com>
> Cc: modperl@apache.org
> Subject: Re: UN-Authenticating users?
>
> On Tue, Feb 15, 2000 at 09:22:20AM -0800, Sean Chittenden wrote:
> > > >I'm using CGI.pm under Apache::Registry, so I don't have a nice $r
> > > >object to see if I could do something like $c->user = ""; which I'm
> > > >guessing would barf anyway.
> >
> > Ugh... CGI.pm? Any chance you could move the use of CGI.pm to
> > Apache::Request? 1001 times faster and doesn't have the code bloat of the
> > HTML generation.
>
> Sorry for the basic question but I'm still learning mod_perl's in and
> outs: what do you mean by "move the use of CGI.pm to Apache::Request" ?
>
> (I couldn't find a man page for Apache::Request on my Debian system)
>
> Cheers,
>
>
--
Sean Chittenden
sean.chittenden@usa.net
(408)530-0001
against CGI.pm.
Apache::Request is a module that you can get via CPAN. It's
purpose is to emulate the core functionality of CGI.pm, except that it
was written in C and consequently is a) much faster and b) has a much
smaller memory foot print. The ONLY downside to it that I have found (but
I never use this feature, so don't care at all) is that Apache::Request
does not allow you to build HTML. Since I use a template solution, I
don't care AT ALL about the lack of the HTML creation feature.
That being said, because CGI.pm is a bloated piece of code, I
typically rewrite or don't use modules that depend on CGI.pm because of
it's size (and because it's slow). Apache::Request behaves the same as
CGI.pm, but the manual will explain more of that when you install it. ;)
--SC
On Thu, 17 Feb 2000, Louis-David Mitterrand wrote:
> Date: Thu, 17 Feb 2000 14:43:33 +0100
> From: Louis-David Mitterrand <cunctator@apartia.ch>
> Reply-To: ldm@aparima.com
> To: Sean Chittenden <sean@serverninjas.com>
> Cc: modperl@apache.org
> Subject: Re: UN-Authenticating users?
>
> On Tue, Feb 15, 2000 at 09:22:20AM -0800, Sean Chittenden wrote:
> > > >I'm using CGI.pm under Apache::Registry, so I don't have a nice $r
> > > >object to see if I could do something like $c->user = ""; which I'm
> > > >guessing would barf anyway.
> >
> > Ugh... CGI.pm? Any chance you could move the use of CGI.pm to
> > Apache::Request? 1001 times faster and doesn't have the code bloat of the
> > HTML generation.
>
> Sorry for the basic question but I'm still learning mod_perl's in and
> outs: what do you mean by "move the use of CGI.pm to Apache::Request" ?
>
> (I couldn't find a man page for Apache::Request on my Debian system)
>
> Cheers,
>
>
--
Sean Chittenden
sean.chittenden@usa.net
(408)530-0001