All,
Thanks for the great explanation for newbies like me! Keep up the good work
On Jan 31, 2008 11:57 AM, Anthony Gardner <[EMAIL PROTECTED]> wrote:
> If you have a vanilla CGI script, every request you make to the webserver
> it's running on, will always create a new instance of that script, r
If you have a vanilla CGI script, every request you make to the webserver it's
running on, will always create a new instance of that script, run it, return
the values in a response and then the script ceases to exist in the server. The
next time a request arrives for that script, the same sequen
Mag Gam wrote:
> I am bit confused. While reading the mod_perl book, I noticed they are
> using Apache::Request versus CGI for form data handling. Why is that? Is
> it recommended to use Apache over CGI? Any advantages? I am using CGI
> because its a standard module.
CGI.pm is old and venerable.
The request object is used in handlers. You can either write handlers or CGI
scripts. Continue using CGI but inorder to reap the benifits of mod-perl, you
will need to run it under ModPerl::Registry.
In your CGI script, while running under ModPerl::Registry., you even have
access to the reque
Hi All,
I am bit confused. While reading the mod_perl book, I noticed they are
using Apache::Request versus CGI for form data handling. Why is that? Is it
recommended to use Apache over CGI? Any advantages? I am using CGI because
its a standard module.
TIA
