StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p><a href="http://search.cpan.org/perldoc/Plack::App::WrapCGI" rel="noreferrer">Plack::App::WrapCGI</a> or <a href="http://search.cpan.org/perldoc/Plack::App::CGIBin" rel="noreferrer">Plack::App::CGIBin</a> represent one way to do this (together with <code>plackup</code> and the default single-threaded Plack HTTP server) but it's not running the CGIs in the context they really expect to be run in (a standalone process) so it's not entirely pretty (the same caveats apply as using modperl registry, more or less). I'm not aware of a pure-perl webserver that actually forks and runs CGI as CGI (nor a non-perl one that does CGI and requires zero config, although lighttpd comes close).</p> <p>The reason why "are you using CGI.pm" is a relevant question is because if you haven't already started the application you might want to consider writing against pretty much <em>anything</em> else, e.g.</p> <ul> <li><a href="http://search.cpan.org/perldoc/Web::Simple" rel="noreferrer">Web::Simple</a></li> <li><a href="http://search.cpan.org/perldoc/CGI::Application" rel="noreferrer">CGI::Application</a></li> <li><a href="http://search.cpan.org/perldoc/Catalyst" rel="noreferrer">Catalyst</a></li> <li><a href="http://search.cpan.org/perldoc/Mason" rel="noreferrer">Mason</a></li> <li><a href="http://search.cpan.org/perldoc/Mojolicious" rel="noreferrer">Mojolicious</a></li> <li><a href="http://search.cpan.org/perldoc/Dancer" rel="noreferrer">Dancer</a></li> </ul> <p>(in random order to hide my obvious favoritism) and gain the ability to easily run the same app as a standalone HTTP server, FastCGI, mod_perl app, or plain CGI if push comes to shove, and without the impedance mismatch that you get when writing to CGI.pm's interface</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload