Kevin van Zonneveld 8489bdbaeb Buggy connections could crash node.js. Now check connection before sending data every time
http://groups.google.com/group/nodejs/browse_thread/thread/16abfa87c32408f3

We have our node.js server monitored by monit, however it seems monit is pretty
agressive / quick about closing its connection and thus we've gotten into a
loop of errors like this:

    at #<a ServerResponse>.flush
    at #<a ServerResponse>.sendBody
    at [object Object].json
    at [object Object].[anonymous]
    at [object Object].[anonymous]
    at [object Object].[anonymous]
http.js:353: Socket is not open for writing
      connection.send(out, out.encoding);
                 ^

Below is a patch that basically cause flushMessageQueue to check the connection
state for each item in the queue rather than just a single time in the
beginning.
2009-08-21 17:54:10 +02:00
2009-08-21 14:53:58 +02:00
2009-08-13 15:52:55 +02:00
2009-07-16 16:54:55 +02:00
2009-07-28 12:36:41 +02:00
2009-07-24 15:14:59 +02:00
2009-07-13 16:38:54 +02:00
2009-08-03 17:51:35 +02:00

Purely evented I/O for V8 javascript.

See http://tinyclouds.org/node for more information.

For help and discussion subscribe to the mailing list at 
http://groups.google.com/group/nodejs or send an email to 
nodejs+subscribe@googlegroups.com.

A list of projects using Node can be found at
http://wiki.github.com/ry/node

To build
./configure
make 
make install
Description
No description provided
Readme 175 MiB