To me, this is a surprisingly tough question to answer. I'd say that the primary use of mod_perl is to speed up your pages via Apache::Registry, Apache::PerlRun or your own handlers. However, it's much more than that. 2 keys for me both personally and professionally are:
1) It allows you to do dynamic Apache configs with <perl> </perl> sections in your httpd.conf. This is VERY cool and this feature alone has saved me many hours of administrative time. 2) It brings a little (or a lot) of CPAN to your Apache setup(s). http://search.cpan.org/search?mode=module&query=Apache. The whole idea of having a perl interpreter spinning inside of your apache basically gives you the ability to do almost anything you can think of. I've heard that there is a version of MySQL which will be using the same concept, but this may just be a rumor. Hope not, sounds like it could be great. That said - write a clean cgi script and do some simple benchmarks. Then wrap it in Apache::Registry and see what happens; it's pretty remarkable. It's likely that it could be all you need ! Anyhow, have a blast. Matt --- [EMAIL PROTECTED] wrote: > > 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? > --Is it to run CGI Scripts under Apache::Registry handler > and just create your own Apache-Handlers on a needed basis, or > -- should the focus be to build all the webpages of the > application as Apache-Handlers and not as CGI Scripts running > under Apache::Registry? > > Thanks, > Rex > __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]