> So what you're saying is basically that under my stress conditions it's possible that I can leave some packet behind that will never get to the server and cause a socket timeout?
The amount of resources in your server are finite. If you throw more at it than it can handle something has to break somewhere. But it will always tell you when that happens with a timeout. Ideally you would throttle the traffic before that happens. Also it is important to do the best you can to clean things up with error-handling code. The client will also be notified of a problem. So the client should retry and preferably back off a bit. With proper error-handling on both sides you should never lose anything in the long run. It will just get slow. Speaking of socket.io, it is very good at not losing stuff. When my app in the client is talking to the server, and I do an abrupt restart, the client keeps the data pending and when the server comes back up it continues with no lost data. -- 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
