mod_perl and legacy code

hesco has asked for the wisdom of the Perl Monks concerning the following question:

I'd like to install RT (requiring mod_perl) on a server which is already running other perl applications. What risks do I face of breaking what I've already got and are there any guides for adapting legacy code to be mod_perl safe?

-- Hugh

if( $lal && $lol ) { $life++; }

Comment on mod_perl and legacy code

Replies are listed 'Best First'.
Re: mod_perl and legacy code by CountZero (Bishop) on Jun 12, 2009 at 06:05 UTC
Unless RT needs versions of other modules that are mutually incompatible with the needs of already running applications, there should be no problem and even then with some juggling of `use lib ..` this can be made to work. Legacy code will probably need to be run under Apache::Registry. The mod_perl site has this documentation: Guide to Porting. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James	[reply] [d/l]
Re: mod_perl and legacy code by ikegami (Patriarch) on Jun 12, 2009 at 06:10 UTC
mod_cgi and mod_perl can coexist on a server. If you continue to run your existing apps using mod_cgi, nothing will break cause nothing will change.	[reply]


Come for the quick hacks, stay for the epiphanies.
	PerlMonks