On Mar 5, 2012, at March 5, 20124:53 PM, Mark Hahn wrote:
> I'm just trying to counter unnecessary FUD.
>
> > 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.
you must mean process.on('uncaughtException'), a try/catch will not catch
errors thrown in callbacks.
>
> --
> 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
--
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
