> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 10:28 AM > To: [EMAIL PROTECTED] > Subject: Mod_Perl -- A very basic question to get started > > > > Hello Friends, > > I have all the web-development done in ASP for W2K with IIS > Web-Servers and > am a newbie to mod_perl. I have a very basic question on this Perl > technology. Here it is: > > What is the primodial or **chief use** of mod_perl > with apache?
To build a complete Perl interpreter into the apache httpd binary, and provide hooks so perl code can be called at various points in the request handling process. > --Is it to run CGI Scripts under > Apache::Registry handler > and just create your own Apache-Handlers on a needed > basis, or This might be the most common use, I dunno. Apache::Registry provides a very nice CGI-like environment that gives you the speed benefits of mod_perl while allowing you to write your scripts like traditional CGI scripts. (Apache::Registry has a few "gotcha's"; the Apache::PerlRun handler is even closer to a pure CGI environment, at some expense in speed). > -- should the focus be to build all the webpages of the > application as Apache-Handlers and not as CGI Scripts > running > under Apache::Registry? Making each page a separate PerlHandler would be counter-productive, as you would need to configure each page separately in httpd.conf If your application is already built as CGI scripts, Apache::Registry has relatively little overhead and is easy to port to. The handler should be though of as a "framework". Apache::Registry gives you a CGI-like framework. HTML::Mason, for example, gives you more of an ASP-like framework. There are others, and you can write your own. I have found Lincoln Stein's book "Writing Apache Modules with Perl and C" to be an invaluable resource. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
