12 messages in ru.sysoev.nginxRe: fastcgi, simply wrong| From | Sent On | Attachments |
|---|---|---|
| Alexandre Girao | Apr 24, 2008 9:11 pm | |
| Maxim Dounin | Apr 25, 2008 1:02 am | |
| Manlio Perillo | Apr 25, 2008 2:58 am | |
| Igor Sysoev | Apr 25, 2008 3:47 am | |
| Igor Sysoev | Apr 25, 2008 4:24 am | |
| Alexandre Girao | Apr 25, 2008 5:03 am | |
| Alexandre Girao | Apr 25, 2008 5:08 am | |
| Alexandre Girao | Apr 25, 2008 5:18 am | |
| Igor Sysoev | Apr 25, 2008 5:26 am | |
| Alexandre Girao | Apr 25, 2008 5:41 am | |
| Maxim Dounin | Apr 25, 2008 5:55 am | |
| Alexandre Girao | Apr 25, 2008 6:05 am |
| Subject: | Re: fastcgi, simply wrong | |
|---|---|---|
| From: | Manlio Perillo (manl...@public.gmane.org) | |
| Date: | Apr 25, 2008 2:58:54 am | |
| List: | ru.sysoev.nginx | |
Alexandre Girao ha scritto:
Hi folks,
i've just dedicated some hours upon the nginx behavior/source code (version 0.6.29, but also happens to 0.5.35) towards fastcgi protocol and discovered that the requestId is fixed, it's simple always equal do 1, this break the the concurrency completely (as i've proved easily) and it also causes early closed connections from the web server/client became out-of-sync with the request state in correctly implemented fastcgi applications, not trying to be unpleasant, but i think that saying that nginx supports fastcgi can do more harm than good to the project.. passing by just to say this, hope you guys find a good solution, im out.
Note that, as far as I know, Apache and Lighttpd *does* not supports multiplexing.
This is not only hard to implement, but it is also not well designed in FastCGI.
There are some comments here: http://twistedmatrix.com/trac/browser/trunk/twisted/web2/channel/fastcgi.py
fastcgi is a good thing, see (and think) for yourself
Well, not all people think that FastCGI is a good thing.
- http://cryp.to/publications/fastcgi/ - http://www.fastcgi.com/devkit/doc/fastcgi-whitepaper/fastcgi.htm - http://www.fastcgi.com/devkit/doc/fcgi-spec.html
Manlio Perillo