I came across an issue today using net.setTimout in a POP3 server written with Node.
The server was set to timeout connections after one minute. A client would start downloading an email, the server would write the email in one go to the socket. The download would take some time for the client, and after a minute it would still be downloading, but the server would timeout the connection and drop the client. In this case there is activity from the client side in terms of reading from the kernel buffer, but from the point of view of Node it would see no activity and timeout the connection. Is that correct? Would it be helpful to flesh out the documentation for setTimeout to highlight issues like this? -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
