Commit 9891811
doc: edit addon text about event loop blocking
PR-URL: #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>1 parent acd78d9 commit 9891811
1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -28,10 +28,10 @@ involving knowledge of several components and APIs: | |||
| 28 | 28 | as interacting with the filesystem, sockets, timers, and system events. libuv | |
| 29 | 29 | also provides a threading abstraction similar to POSIX threads for | |
| 30 | 30 | more sophisticated asynchronous addons that need to move beyond the | |
| 31 | - standard event loop. Addon authors are encouraged to think about how to | ||
| 31 | + standard event loop. Addon authors should | ||
| 32 | 32 | avoid blocking the event loop with I/O or other time-intensive tasks by | |
| 33 | - off-loading work via libuv to non-blocking system operations, worker threads | ||
| 34 | - or a custom use of libuv's threads. | ||
| 33 | + offloading work via libuv to non-blocking system operations, worker threads, | ||
| 34 | + or a custom use of libuv threads. | ||
| 35 | 35 | ||
| 36 | 36 | * Internal Node.js libraries. Node.js itself exports C++ APIs that addons can | |
| 37 | 37 | use, the most important of which is the `node::ObjectWrap` class. | |
0 commit comments