doc: edit addon text about event loop blocking

PR-URL: https://github.com/nodejs/node/pull/36448
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Shelley Vohr <codebytere@gmail.com>
pull/36448/head
Rich Trott 2020-12-08 10:49:15 -08:00
parent 7c702f8db6
commit e28f23f39f
1 changed files with 3 additions and 3 deletions

View File

@ -28,10 +28,10 @@ involving knowledge of several components and APIs:
as interacting with the filesystem, sockets, timers, and system events. libuv
also provides a threading abstraction similar to POSIX threads for
more sophisticated asynchronous addons that need to move beyond the
standard event loop. Addon authors are encouraged to think about how to
standard event loop. Addon authors should
avoid blocking the event loop with I/O or other time-intensive tasks by
off-loading work via libuv to non-blocking system operations, worker threads
or a custom use of libuv's threads.
offloading work via libuv to non-blocking system operations, worker threads,
or a custom use of libuv threads.
* Internal Node.js libraries. Node.js itself exports C++ APIs that addons can
use, the most important of which is the `node::ObjectWrap` class.