On Fri, 2004-02-13 at 13:49, Morbus Iff wrote: > * You're starting a script. It needs to > run under CGI and mod_perl. Would you > > * convince the user to go mod_perl or nothing else. > * maintain two codebases, one for mod_perl, one for cgi.
If you really have to handle both mod_perl and CGI, then Apache::Registry is a reasonable way to go. > * You're starting a new project under mod_perl. There are many different frameworks you could choose for that, from mod_perl handlers to Apache::ASP. Take a look on the mod_perl site for more. - Perrin -- 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
