You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Frédéric SCHWIEN <fr...@igtech.fr> on 2002/08/18 13:49:07 UTC

RE : Mod_perl Application Development

Check CGI::Application from CPAN,

Very useful. It uses differents "Run Mode" for Application. Originally,
it uses HTML::Template, but can be easily subclassed to use another
Template System. We use it with Text::Template.

Fred



-----Message d'origine-----
De : Jonathan Lonsdale [mailto:jon3001@iname.com] 
Envoyé : dimanche 18 août 2002 01:31
À : modperl@perl.apache.org
Objet : Mod_perl Application Development


I'm curious to know how people approach application development with
mod_perl in situations where there could be dozens of distinct
screens/interfaces. I'm currently using the HTML::Template system.

Here's a few approaches I thought of:

1. Single monolithic content handler. Could be hard to maintain. 2.
Distinct content handlers each with their own Location directive. Could
be a pain to maintain the server config. 3. Take a small performance hit
and use an Apache::Registry script for each screen to handle the content
phase. Use 'PerlSetupEnv Off', $r and Apache:: modules and don't bother
being backwardly compatible with CGI.

Thanks,
Jonathan