On Wed, Jun 06, 2007 at 04:57:49PM +0200, Manlio Perillo wrote:
Wayne E. Seguin ha scritto:
On Jun 06, 2007, at 08:55 , Manlio Perillo wrote:
Hi.
In the wiki it is explained that CGI is not supported because is is
slow and not scalable.
This is true, however this should not be a problem for nginx since
process can be handled asyncronously.
CGI is a standard, and many web scripts only support CGI.
Run one or more servers that do support the cgi and proxy to them.
Having to run another server is what I want to avoid.
Implementing CGI support requires:
1) process manager, that will spawn to run CGIs (spawning usual workers
is not effective: they may be huge, they may have many open files that
should be FD_CLOEXEC'ed, etc),
2) ngx_http_cgi_module.
It may take week of thinking and about 40 hours of coding.
THe thinking is easy for me: I can think 12 hours and more per day,
but productive coding is very hard. I simply have no many productive hours.
I have too many things to implement and CGI has the lowest priority of them
and I do not want to spend productive hours for it.