doc: don't recommend domains for error handling

Remove the suggestion to use domains for exception handling. Add clarity
to "unhandledException".

Fixes: https://github.com/nodejs/io.js/issues/2055
PR-URL: https://github.com/nodejs/io.js/pull/2056
Reviewed-By: Trev Norris <trev.norris@gmail.com>
Reviewed-By: Chris Dickinson <chris@neversaw.us>

diff --git a/doc/api/process.markdown b/doc/api/process.markdown
index ebff3d6496a6442921ee09c30eb5db8130d9ca8a..71c7d3cfcc76b18dcd4112df934e6192c2c133df 100644 (file)
--- a/doc/api/process.markdown
+++ b/doc/api/process.markdown
@@ -104,9 +104,6 @@ Example of listening for `uncaughtException`:
 Note that `uncaughtException` is a very crude mechanism for exception
 handling.
 
-Don't use it, use [domains](domain.html) instead. If you do use it, restart
-your application after every unhandled exception!
-
 Do *not* use it as the io.js equivalent of `On Error Resume Next`. An
 unhandled exception means your application - and by extension io.js itself -
 is in an undefined state. Blindly resuming means *anything* could happen.
@@ -114,6 +111,11 @@ is in an undefined state. Blindly resuming means *anything* could happen.
 Think of resuming as pulling the power cord when you are upgrading your system.
 Nine out of ten times nothing happens - but the 10th time, your system is bust.
 
+`uncaughtException` should be used to perform synchronous cleanup before
+shutting down the process. It is not safe to resume normal operation after
+`uncaughtException`. If you do use it, restart your application after every
+unhandled exception!
+
 You have been warned.
 
 ## Event: 'unhandledRejection'