doc: explain Worker semantics in async_hooks.md

PR-URL: #20876 Reviewed-By: Gireesh Punathil <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Shingo Inoue <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Tiancheng "Timothy" Gu <[email protected]> Reviewed-By: John-David Dalton <[email protected]> Reviewed-By: Gus Caplan <[email protected]>
nodejs · Jun 13, 2018 · 6caa354 · 6caa354
1 parent ed05d9a
commit 6caa354
Showing 1 changed file with 5 additions and 1 deletion.
diff --git a/doc/api/async_hooks.md b/doc/api/async_hooks.md
@@ -21,6 +21,9 @@ A resource can also be closed before the callback is called. `AsyncHook` does
 not explicitly distinguish between these different cases but will represent them
 as the abstract concept that is a resource.
 
+If [`Worker`][]s are used, each thread has an independent `async_hooks`
+interface, and each thread will use a new set of async IDs.
+
 ## Public API
 
 ### Overview
@@ -224,7 +227,7 @@ clearTimeout(setTimeout(() => {}, 10));
 ```
 
 Every new resource is assigned an ID that is unique within the scope of the
-current process.
+current Node.js instance.
 
 ###### `type`
 
@@ -725,3 +728,4 @@ never be called.
 [Hook Callbacks]: #async_hooks_hook_callbacks
 [PromiseHooks]: https://docs.google.com/document/d/1rda3yKGHimKIhg5YeoAmCOtyURgsbTH_qaYR79FELlk
 [promise execution tracking]: #async_hooks_promise_execution_tracking
+[`Worker`]: worker.html#worker_worker