mod_perl and cgi detente

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

Replies are listed 'Best First'.
Re: mod_perl and cgi detente by perrin (Chancellor) on Mar 26, 2007 at 20:36 UTC
Is there any reason you aren't looking to wrap your old CGI apps in ModPerl::PerlRun or ModPerl::Registry? That's usually what people do when they move them over. Aside from that, you'll have to tell us what isn't porting cleanly from your CGIs in order to get advice. I saw that you mentioned CGI.pm vs. Apache::Request for parsing params. They are intended to offer essentially the same API. If you want them to be exactly the same, just CGI.pm in all cases. It works fine under mod_perl and the performance difference is not significant for most sites.	[reply]
Re: mod_perl and cgi detente by Joost (Canon) on Mar 26, 2007 at 19:34 UTC
Are there specific issues you're dealing with? If you build your app on CGI.pm (or CGI::Application etc), use DBI with Apache::DBI or some other persistance-checking technique and load your modules as early as possible you've probably got most of the performance enhancements for free without doing anything apache specific - ie. your code should work both as CGI and as Apache::Registry modules. "What should it profit a man, if he should win a flame war, yet lose his cool?"	[reply]
Re^2: mod_perl and cgi detente by derby (Abbot) on Mar 26, 2007 at 19:48 UTC
I'm looking into building a Sessions module that can sit over a namespace (mod_perl) or be called from a cgi script (before or after the CGI creation) -- So I'm looking to do a Foo::Session instead of Foo::Session::Apache and Foo::Session::Cgi. Now if the session was simple, it would be straightforward (get cookie, set cookie); however, sometimes I need to store GET params in the session and I may need to redirect if the session is invalid. So sometimes I have an Apache request object to deal with sometimes, a CGI object. -derby	[reply]
Re^3: mod_perl and cgi detente by rhesa (Vicar) on Mar 26, 2007 at 20:32 UTC
Are you sure you will need to go through all that trouble? CGI is aware of mod_perl, and will use the appropriate Apache modules under the hood. You can even access the request object through `$cgi->r`. I would just write the code as if it's going to run as plain CGI, and let CGI.pm and mod_perl handle their environment for me.	[reply] [d/l]
Re: mod_perl and cgi detente by Khen1950fx (Canon) on Mar 26, 2007 at 19:55 UTC
I found a link that might help you: CGI to mod_perl Porting: mod_perl Coding Guidelines	[reply]
Re: mod_perl and cgi detente by randyk (Parson) on Mar 26, 2007 at 20:41 UTC
I'm working on a module - CGI::Apache2::Wrapper - which may help in this regard. The aim here is to provide a (mostly) CGI.pm-compatible interface to certain mod_perl2 and libapreq2 methods. Currently the main one present is param(), but work is being done on others like cookie() and upload(). One of the main purposes is to assist in the porting of apps from cgi to mod_perl, so that one can say in a handler `my $cgi; if ($I_want_to_use_mod_perl_modules) { $cgi = CGI::Apache2::Wrapper->new($r); } else { $cgi = CGI->new($r); }` [download] and then call methods like param(), etc. on the $cgi object, with the work of loading and calling the appropriate mod_perl2/libapreq2 modules and methods done behind the scenes. Let me know if there's something along these lines that would be useful.	[reply] [d/l]
Re: mod_perl and cgi detente by philcrow (Priest) on Mar 26, 2007 at 20:26 UTC
You might consider a framework like Catalyst or Gantry which factor out the server engine. But they might require more re-writing than you want to do. Phil	[reply]
Re: mod_perl and cgi detente by cbrandtbuffalo (Deacon) on Mar 26, 2007 at 20:13 UTC
Are you working with Apache/mod_perl 1 or 2?	[reply]


more useful options
	PerlMonks