> and eventually ending in timeout exception (socket timeout) I missed this in the last reading of your post. Yes, HTTP can timeout and give you an error. This does happen under stress.
I thought you said in your OP that it would hang and not return any error. Many developers throttle how much load they will accept and return a message saying they are overloaded and to come back later. This way they stay below the threshold of load where timeouts happen. -- 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
