in reply to CGI Replacement Recommendations?

Slightly building off the OP's question:

Are technologies like Mojolicous, Catalyst or Perl Dancer a replacement or enhancement for CGI? This is the thing (admittedly one of many) I get confused about.

I downloaded and installed Mojolicious last night. I've read through the site and joined the mailing list a few weeks back. As far as I can tell it 'supports' CGI, mod_perl, and FastCGI.

So does this mean that the OP would be able to happily take his CGI scripts and have them run nicely under Mojolicious or will he have to learn something new? Would someone like me who has fumbled around with PHP for a few years need to go back and learn CGI first or could I just get going with Mojolicious (or Dancer etc.)?

As much as I've searched there doesn't seem to be clear analysis of this.


"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." — Don Quixote

Replies are listed 'Best First'.
Re^2: CGI Replacement Recommendations?
by Corion (Patriarch) on Feb 09, 2011 at 15:32 UTC

    These three are "middleware" frameworks that can adapt CGI (or a stand-alone server, or mod_perl, or FCGI, etc.) to some internal, "unified" structure, more often based on a class hierarchy or a dispatch hierarchy than not. CGI "only" structures its path hierarchy using the file system, and launches a new process for every request, while other protocols have persistent processes between requests.