catch exceptions where they appear first, thats the best place to handle them. I add the handler for the uncaughtExceptions event only to get awareness where the exception comes from, to handle it there. and, yeah, domains :)
Am Mittwoch, 16. Januar 2013 19:51:28 UTC+1 schrieb mjosephd: > > Hi All, > > In node.js the server crashes whenever an exception is thrown, I also read > up that it IS possible to catch uncaught exceptions but the best practice > is to do any necessary precautions such as logging details and then > restarting the server. However if multiple users are performing various > actions this would have the system become inconsistent, for example a > transaction (multiple db calls for one process) was taking place and the > server restarted in the middle, multiple web service call for the same > process and again the server restarted in the middle and such similar > scenarios. > > At the moment we are considering of using node.js for an enterprise > solution which involves multiple requests from multiple users very often to > the node.js server and it is also critical that no data is saved > incorrectly either. This is the only hurdle so far I see and would like to > know the best way of handling uncaught exceptions considering that multiple > users will be sending many requests regularly to the node.js server. > > Regards, > Mjosephd > -- 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
