From 6caa3543774dcfb246dc50b20cdd5aa4ee854cc8 Mon Sep 17 00:00:00 2001 From: Anna Henningsen Date: Tue, 22 May 2018 21:47:06 +0200 Subject: [PATCH] doc: explain Worker semantics in async_hooks.md PR-URL: https://github.com/nodejs/node/pull/20876 Reviewed-By: Gireesh Punathil Reviewed-By: Benjamin Gruenbaum Reviewed-By: Shingo Inoue Reviewed-By: Matteo Collina Reviewed-By: Tiancheng "Timothy" Gu Reviewed-By: John-David Dalton Reviewed-By: Gus Caplan --- doc/api/async_hooks.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/doc/api/async_hooks.md b/doc/api/async_hooks.md index 3a6a44d0f71a0d..29dd5259415ac3 100644 --- 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