atom feed12 messages in ru.sysoev.nginxfastcgi, simply wrong
FromSent OnAttachments
Alexandre GiraoApr 24, 2008 9:11 pm 
Maxim DouninApr 25, 2008 1:02 am 
Manlio PerilloApr 25, 2008 2:58 am 
Igor SysoevApr 25, 2008 3:47 am 
Igor SysoevApr 25, 2008 4:24 am 
Alexandre GiraoApr 25, 2008 5:03 am 
Alexandre GiraoApr 25, 2008 5:08 am 
Alexandre GiraoApr 25, 2008 5:18 am 
Igor SysoevApr 25, 2008 5:26 am 
Alexandre GiraoApr 25, 2008 5:41 am 
Maxim DouninApr 25, 2008 5:55 am 
Alexandre GiraoApr 25, 2008 6:05 am 
Subject:fastcgi, simply wrong
From:Alexandre Girao (alex@public.gmane.org)
Date:Apr 24, 2008 9:11:03 pm
List:ru.sysoev.nginx

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.

fastcgi is a good thing, see (and think) for yourself

- http://cryp.to/publications/fastcgi/ - http://www.fastcgi.com/devkit/doc/fastcgi-whitepaper/fastcgi.htm - http://www.fastcgi.com/devkit/doc/fcgi-spec.html

"rationality and objectivity is greatly discredited in these days" -- George Soros