On Mar 5, 2012, at 4:53 PM, Mark Hahn wrote: > I'm just trying to counter unnecessary FUD.
Agree on countering FUD. I've been building with Node for a year now and found it a great question. "None" might be the answer, but that must be backed with why or else the community comes across as zealots. :) > > > That works if all the work is synchronous. Node really shines for async > > operations, which the try-catch loop on the page does not catch. > > I have an exception handler at the root of the app that catches them all and > I have one around the page call. It never occurred to me that the page one > is almost useless (duh). I have never gotten an unhandled exception in my > 1.5 years of node usage so my try-catches haven't exactly been tested. If a module you are using has gotten itself into a mess, there may be little you can do to recover at the app level and you will need to restart the whole node process. I don't see the root exception handing in much example code out there, nor have a seen much discussion besides a thread a while back about default behavior for when an exception occurs. I consider myself a novice in this area and would love to see more docs / examples on best practices. Having said that, there may be few if any architectural differences between a well written app that can fail multiple outstanding requests and a single request -- leading to no disadvantage here for Node. Any other disadvantages (perceived or real) would be useful to flesh out. :) -- Dick -- 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
