[Nitro] Q about mongrel && nitro

Fang Sun nusgnaf at gmail.com
Fri Aug 4 21:55:59 EDT 2006

Digging mongrel rdoc I found these interesting remarks on
Mongrel::HttpResponse implementation:
"You may also work the HttpResponse object directly using the various
attributes available for the raw socket, body, header, and status
codes. If you do this you're on your own. A design decision was made
to force the client to not pipeline requests. HTTP/1.1 pipelining
really kills the performance due to how it has to be handled and how
unclear the standard is. To fix this the HttpResponse gives a
"Connection: close" header which forces the client to close right
away. The bonus for this is that it gives a pretty nice speed boost to
most clients since they can close their connection immediately."

So, it seems that mongrel close the client connection mainly for
performance reason.

More information about the Nitro-general mailing list