No matter how much stress a NodeJS app is subjected to, it should only offer 2 responses:
1.) the correct data 2.) a SocketTimeout exception A NodeJS app which sends back bad data is useless. I'm trying to find an answer for the problem described here: http://www.smashcompany.com/technology/a-surprising-nodejs-failure-mode-deterministic-code-becomes-probabilistic-under-load Any thoughts on why this might happen when the load is high enough? -- Job board: http://jobs.nodejs.org/ New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md Old group rules: 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/a02a9f1f-ef00-4049-8669-b70a00bf9457%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
