No such thing as a small change | |
PerlMonks |
how to migrate a large perl 4ish CGI site to mod_perlby qq (Hermit) |
on Jun 19, 2004 at 13:53 UTC ( [id://368172]=perlquestion: print w/replies, xml ) | Need Help?? |
qq has asked for the wisdom of the Perl Monks concerning the following question: I'm working on a large, dynamic web site thats written in a perl 4ish style. No strict, warnings, modules, OO, templating or even CGI.pm. Lots of global variables, subs called with &do_something; syntax (accessing enclosing @_), database access on every page with hardcoded dbi strings. In short, the very opposite of what the monks consider good style. It does, however, work (albeit with a few dropped database connections and a bit slow.) The current environment is perl 5.8.3, apache 2. The wish is to migrate to mod_perl and clean it up. The minimal option is to clean each page that breaking under mod_prel or when new functionality is needed. Add strict, warnings, obvious modules (CGI.pm?), but still keeping it as CGI-ish, and letting the Registry modules handle the mod perl integration. The maximul option is to redesign the site from scratch, using mason or Template Toolkit. Then flip the switch. This seems like overkill unless serious new functionality is being considered. The question is - how much to do, and how to do it. A hybrid approach seems possible, but perhaps more difficult to plan. Can you slowly transform a legacy site into something that looks freshly built? Any advice on strategies, tips, pitfalls, resources (is Practical mod_perl worth the read?), etc., much appreciated. There are interersting CGI/mod_perl discussions at these nodes 174307, 253921, 367315, and the official porting guidelines. thanks, qq
Back to
Seekers of Perl Wisdom
|
|