From: "Stefan Hornburg (Racke)" <[email protected]>
On 05/03/2014 08:00 AM, Octavian Rasnita wrote:
From: "Joel Roth" <[email protected]>
Stefan Hornburg (Racke) wrote:
CGI is old and should die though. Even if you are stuck with it,
FastCGI is a more viable and faster way to run CGI scripts.
For testing, and for newbies, CGI is still convenient.
I do experience a fairly long lag while pages are loaded.
Greetings
Joel
When we are talking on a mailing list dedicated to a web framework so we
are probably thinking to use CGI with a web framework, then yes, CGI is
not recommended.
But not all the sites use a CMS or web framework or ORM, or templating
system.
There may be very simple scripts which are used just once a week or
month, and not by the public but by a sysadmin for doing some settings.
In those cases using CGI is better than psgi, because they are more
convenient to create and don't stay loaded in memory and consume
resources for no reason.
And I don't see why CGI should die while for those sysadmins is more
helpful than other solutions.
I don't use any CGI scripts for my sysadmin part of work, but of course
normal Perl scripts
executed from the command line or cron.
Some of these are now written in Dancer, which is useful to share
configuration and modules
with your web projects.
I don't mind people using CGI, but I don't see a purpose of them for my
work.
Regards
Racke
I also don't use CGI... usually, but in some cases the sysadmin just offers
a directory where you can place CGI scripts that will be loaded by Apache,
because they need to be used by non-technical people to input some data once
in a while.
So CLI scripts are not a solution, mod_perl/fastcgi/psgi are not a solution
either, and even if they would be, CGI would still be easier for simple
scripts. And they can also share configuration files, use different modules
etc.
Octavian
_______________________________________________
dancer-users mailing list
[email protected]
http://lists.preshweb.co.uk/mailman/listinfo/dancer-users
