[cgiapp] CGI::Application wiki page CatalystCompared updated byJackTean

[Ron Savage]

Hi Octavian

On Mon, 2011-05-16 at 09:52 +0300, Octavian Rasnita wrote:
> From: "Ron Savage" <ron at savage.net.au>
> > Hi Octavian
> >
> > On Mon, 2011-05-16 at 08:24 +0300, Octavian Rasnita wrote:
> >> The link
> >>
> >> http://people.plusthree.com/~perrin/mvc_samples.tgz
> >>
> >> to the code samples doesn't work. I don't know if it is a temporary 
> >> problem
> >> or if it happends only to me...
> >
> > No response for me, either.
> >
> >> BTW, the comparison tells only about mod_perl, but nothing about FastCGI 
> >> nor
> >> about PSGI.
> >
> > Sooooooo, you're offering to remedy that I take it :-))?
> 
> 
> I would.. if I could. :-)
> But I can't compare because I don't know if C::A supports it or not.
> 
> Catalyst supports FastCGI natively and PSGI by Catalyst::Engine::PSGI.

CGI::App doesn't have in it any special code which checks the
environment it's runnning under, as far as I'm aware - a quick check of
the source revels nothing.

With Apache (V 2), you can simply use Apache::Registry to get a
significant speedup.

Your CGI script does not need changes.

Of course, the fact that you don't change the script means it is not
able to take advantage of any other (apart from speed) capabilities of
Apache.

But then, most CGI scripts don't need those capabilities.

By using a web server/add-on combination as a replacement for Apache,
you get the same speed up, but without the memory overhead of Apache.

Obviously, you can't then get access to Apache-specific capabilities.

CGI::Application::Dispatch::PSGI gives any CGI script using CGI::App
access to PSGI's amazing capabilities. It's what I use for every CGI
script, nowadays.

plackup also supports FastCGI.

What's not to like :-)?

-- 
Ron Savage
http://savage.net.au/
Ph: 0421 920 622