Jesse Erlbaum wrote:
Philippe --
Check out the guide: Check out the books: Check out the success stories:
Is that your answer? I was hoping for specific examples, not hand-waving.
I like to think that Part III (Chapters 11-17) of the mod_perl Developer's Cookbook does some of that.
authentication is a good example of how mod_perl enables life outside of CGI scripting. if you require authentication in your application, auth handlers allow you to entirely remove authentication from your content handlers.
mod_perl allows you to let your content handlers to focus on content - all other parts of your application (authentication, session management, proxying, URL rewriting tricks, etc) can programmed at the server level via other parts of the request cycle.
I'm talking about this at a very basic level at OSCon this year (as I did last year), but you might be interested in my slides from YAPC2002 to get a general feel for it (and ApacheCon if you want to see the more twisted side of what mod_perl opens up).
http://www.modperlcookbook.org/~geoff/slides/
HTH
--Geoff
