On Fri, Mar 30, 2012 at 22:20, Mikeal Rogers <[email protected]> wrote: > > On Mar 30, 2012, at March 30, 201212:47 PM, Ben Noordhuis wrote: > >> On Fri, Mar 30, 2012 at 17:33, Masiar <[email protected]> wrote: >>> Thanks! Now I know what to do. I checked the connections to the >>> clients and already seem to be keep-alive (from liveHTTPHeaders) >>> without me setting it manually on both sides, can you tell me how to >>> set a timeout for incoming requests? Thanks. >> >> HTTP keep-alive is not related to TCP keep-alive. HTTP keep-alive >> tells the server to keep the connection open after the request is >> finished. TCP keep-alive is a mechanism to keep TCP connections open >> (efficiently) for long periods of time. >> >> req.connection.setTimeout() lets you set the timeout in your server. > > You can't use req.connection reliably in 0.6 because the socket is assigned > after nexTick() which is why we have req.setTimeout which binds after the > socket is assigned.
There is no IncomingMessage.prototype.setTimeout() method in v0.6 or master. (Omission? Probably.) -- 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
