Please let me raise a question. In practice, people who can program in other phases usually can 1) program directly in C module; and 2) find that C provides much better a solution.
For example, the authz phase in the dual-Apache setup. Here the static files are served by the light Apache. A C autenz handler is usually more efficient and may be a must. The same is true for the URL re-writing phase. Most likely we need the URL to be re-written for both dynamic contents and static files. So, while mod_perl is able to handle other phases, in practice, one may still need to go back to the C API for the best results. In the content phase, I think the OO programming, and so the MVC (Model-View-Control) concept, makes mod_perl much better a choice than PHP for large projects. ------------------------------------------------------------- Author: Randal L. Schwartz <[EMAIL PROTECTED]> Date: 30 Nov 2004 06:29:25 -0800 I just finished transcribing my 90-minute "intro to mod_perl" talk into a three-part series for Linux Magazine... it's dribbling out over the next few months, and will be on my website shortly after the embargo has passed. It's always been clear to me that the real power of mod_perl wasn't the content phase... there are so many OTHER cool things that mod_perl does, and mod_php and mod_cgi and mod_fastcgi can't touch that. -- Report problems: http://perl.apache.org/bugs/ Mail list info: http://perl.apache.org/maillist/modperl.html List etiquette: http://perl.apache.org/maillist/email-etiquette.html
