11 messages in ru.sysoev.nginxRe: [ANN] Enhanced Gentoo ebuilds for...
FromSent OnAttachments
Adrian PerezMay 13, 2008 5:10 pm 
Kingsley ForemanMay 13, 2008 5:42 pm 
Manlio PerilloMay 14, 2008 12:50 am 
Phillip B OldhamMay 14, 2008 1:01 am 
Igor SysoevMay 14, 2008 1:05 am 
Manlio PerilloMay 14, 2008 1:12 am 
Grzegorz NosekMay 14, 2008 1:14 am 
Manlio PerilloMay 14, 2008 1:31 am 
Manlio PerilloMay 14, 2008 1:39 am 
Grzegorz NosekMay 14, 2008 1:47 am 
Adrian PerezMay 14, 2008 3:25 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [ANN] Enhanced Gentoo ebuilds for nginx 0.6.31Actions...
From:Manlio Perillo (manl@public.gmane.org)
Date:May 14, 2008 1:31:26 am
List:ru.sysoev.nginx

Igor Sysoev ha scritto:

On Wed, May 14, 2008 at 09:51:11AM +0200, Manlio Perillo wrote:

By the way, if someone is interested I'm starting to write a CGI module (and, of course, in a very non orthodox way)!

How do you want to implement it ? Forking entire worker it seems overkill for me: you need to close all connections or use FD_CLOEXEC for every socket/etc.

Yes, this is one of the main problems. But it is not stricly necessary to close all the opened connections.

The open syscall should return a file descriptor that is the lowest file descriptor not currently open for that process, so maybe it is safe to just close the first 256 descriptors.

Of course there should be a timer that make sure to close the child process when it timeouts, to avoid a CGI program to stay alive for too much time.

I thought about special CGI manager, but it almost the same as proxying to mini_httpd (http://acme.com/software/mini_httpd/).

Right, it will always be the same as proxying to an external http server, but the advantage is that all can be done without having to use external servers.

Moreover, since I'm mainly a Python programmer, I will try to implement special support for executing Python CGIs without having to to call exec.