It's probably worth pointing out that there is now an increasing trend toward higher level frameworks like Meteor and DerbyJS which help blur the lines between the server and client and simplify the creation of real-time apps. I think in a couple more years they will start to replace Express as the de facto framework to use for medium to large sized projects.
Aspects of Building a Node.js Application
21–22 of 22 posts
Re: Aspects of Building a Node.js Application
#22Earlier quoted context omitted.
When your nodejs instances are crashing several times an hour due to facebook randomly returning html instead of json and the 3rd party library crashing as a result, who has time for maturity? =)
Wouldn't a simple uncaughtException handler be sufficient to prevent most crashes? process.on('uncaughtException', function (err) { // log it });
From the documentation:
"Don't use it, use domains instead. If you do use it, restart your application after every unhandled exception!"
http://nodejs.org/api/process.html#process_event_uncaughtexc...