You are viewing a plain text version of this content. The canonical link for it is here.

Posted to modperl@perl.apache.org by lists user <pr...@gmail.com> on 2007/09/20 08:22:39 UTC

why need apache::request?

I have another question,since we have modperl's full features,why we
need Apache::Request yet?
Thanks.

Re: why need apache::request?

Posted by lists user <pr...@gmail.com>.

2007/9/20, Philippe M. Chiasson <go...@ectoplasm.org>:
> lists user wrote:
> > I have another question,since we have modperl's full features,
>
> Depends on how you define full features ;-)
>
> > why we
> > need Apache::Request yet?
>
> It's called Apache2::Request now for mod_perl 2. Main reason to want to
> use it is to deal with client data. POST/GET/cookie data is not fully parsed by
> mod_perl 2, and Apache2::Request does a mighty good job at taking care
> of that. It's a much better/faster alternative to using CGI.pm
>

Thank you for the kind answer.

--jenifer

Re: why need apache::request?

Posted by "Philippe M. Chiasson" <go...@ectoplasm.org>.

lists user wrote:
> I have another question,since we have modperl's full features,

Depends on how you define full features ;-)

> why we
> need Apache::Request yet?

It's called Apache2::Request now for mod_perl 2. Main reason to want to
use it is to deal with client data. POST/GET/cookie data is not fully parsed by
mod_perl 2, and Apache2::Request does a mighty good job at taking care
of that. It's a much better/faster alternative to using CGI.pm

------------------------------------------------------------------------
Philippe M. Chiasson     GPG: F9BFE0C2480E7680 1AE53631CB32A107 88C3A5A5
http://gozer.ectoplasm.org/       m/gozer\@(apache|cpan|ectoplasm)\.org/