At 11:32 AM 6/10/02 -0700, Bill Moseley wrote:
>>> * Another issue is that while many people come to mod_perl via the >>> registry family, this is not the feature that should come up first, >>> >>> "Easily create custom modules that become part of Apache" >>> "Gain access to all request stages" >>> >>> should probably come before registry.
I'd side with Per on this, Stas. I think it's good to show a simple CGI script converted to Apache::Registry first.
+1. Nothing fancy, just a solid example. Something more than a hello world, but not too complicated.
(BTW -- it was Apache::Registry that allowed me to demo an existing CGI application which was then approved to move to mod_perl.)
IMHO, Registry is the killer app for mod_perl. You get a huge speedup from the caching and you can still control Apache's inner workings via my $r = Apache->request. Most people have a huge number of existing scripts that can benefit from registry, usually with (somewhat) minor modifications. I know that is certainly the case here at my work.
Of course, PerlRun is nice too because we haven't had the time to clean up everything, and might never do so. :-)
Drew
====================================================================== Drew Taylor | Freelance web development using http://www.drewtaylor.com/ | perl/mod_perl/MySQL/postgresql/DBI mailto:[EMAIL PROTECTED] | Email jobs at drewtaylor.com ---------------------------------------------------------------------- Speakeasy.net: A DSL provider with a clue. Sign up today. http://www.speakeasy.net/refer/29655 ======================================================================
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
