19 messages in ru.sysoev.nginxRe: Is mod_php walking on its road?
FromSent OnAttachments
Steve ChuOct 23, 2007 2:01 am 
Aleksandar LazicOct 23, 2007 2:12 am 
Igor SysoevOct 23, 2007 2:15 am 
marc...@public.gmane.orgOct 23, 2007 2:24 am 
Alejandro VartabedianOct 23, 2007 2:42 am 
Manlio PerilloOct 23, 2007 2:46 am 
Igor SysoevOct 23, 2007 3:03 am 
Igor SysoevOct 23, 2007 3:05 am 
Manlio PerilloOct 23, 2007 3:27 am 
Steve ChuOct 23, 2007 3:51 am 
Alejandro VartabedianOct 23, 2007 4:03 am 
Manlio PerilloOct 23, 2007 4:05 am 
Steve ChuOct 23, 2007 7:13 pm 
Yusuf GoolamabbasOct 24, 2007 1:01 am 
Igor SysoevOct 24, 2007 3:14 am 
Steve ChuOct 24, 2007 8:22 am 
Thomas SeifertOct 24, 2007 8:50 am 
Igor SysoevOct 30, 2007 1:11 am 
Manlio PerilloOct 30, 2007 4:35 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: Is mod_php walking on its road?Actions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:Oct 30, 2007 1:11:37 am
List:ru.sysoev.nginx

On Wed, Oct 24, 2007 at 08:22:52AM -0700, Steve Chu wrote:

I mean, why mod_perl not blocked?

As it was already said, ngx_http_perl_module of course blocks too. However, ngx_http_perl_module allows to create call-back handlers that will be called lately. Currently ngx_http_perl_module support two such handlers only:

$r->has_request_body(handler) and $r->sleep(milliseconds, handler)

Use of $r->has_request_body() you may see here: http://wiki.codemongers.com/NginxEmbeddedPerlModule

On 10/24/07, Igor Sysoev <is-G@public.gmane.org> wrote:

On Wed, Oct 24, 2007 at 10:14:19AM +0800, Steve Chu wrote:

What about mod_perl?

There is experimenatl ngx_http_perl_module: http://wiki.codemongers.com/NginxEmbeddedPerlModule

On 10/23/07, Manlio Perillo
<manlio_perillo-VGgt2q2+T+FeoW@public.gmane.org> wrote:

Steve Chu ha scritto:

Sorry,all I made a mistake, nginx is using epoll, so blocked I/O will be a big problem.

Not a "really big" problem, since nginx can use multiple worker processes.

Of course mod_wsgi *should* not be used in the "main" http server, but it should be used "standalone", as a replacement for a "builtin" server and behind another nginx proxy if possible.

With Python this is very effective, since all Python http servers are written in pure Python and use a thread based model.

With PHP the builtin server is written in C, and uses a prefork model (if I'm right) so I don't know is a nginx mod_php is worth the effort.