fastcgi, simply wrong

[Alexandre Girao]

On Fri, Apr 25, 2008 at 6:59 AM, Manlio Perillo
<manlio_perillo at libero.it> wrote:
> 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
>
>

i wont argue on the competency of the code and comments of that guy,
im interested in technical superiority and i found it in fastcgi
protocol for highly dynamic web applications.

>
>
>
> >
> >
> > fastcgi is a good thing, see (and think) for yourself
> >
> >
>
>  Well, not all people think that FastCGI is a good thing.
>

when i said "think for yourself", i was addressing it exactly to
people like you, no offense, just a tip.

>
>
>
> > - 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
>
>