GeezerVison is showing github.com — doc: edit addon text about event loop blocking · nodejs/node@681d2a7
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/api/addons.md +3-3Lines changed: 3 additions & 3 deletions - Display the source diff
- Display the rich diff
| 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. |
|