From edd3b6bc34f211bd3d58642d0c69ce1b5bb9dc3b Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 9 Oct 2025 01:22:20 +0000 Subject: deploy: 9c834956456924df7c885ab8b79573721acaff5c --- ref/api/thread.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'ref/api/thread.html') diff --git a/ref/api/thread.html b/ref/api/thread.html index 9c5104e6..83599d30 100644 --- a/ref/api/thread.html +++ b/ref/api/thread.html @@ -279,7 +279,7 @@ Blocking NNG library calls can however be made safely from NNG

The system may impose limits on the number of threads that can be created. Typically applications should not create more than a dozen of these. If greater concurrency or scalability is needed, consider instead using -an asynchronous model using nng_aio structures.

+an asynchronous model using nng_aio structures.

Thread Structure

typedef struct nng_thread nng_thread;
@@ -287,7 +287,7 @@ an asynchronous model using 
 
The nng_thread structure represents a thread, which is a single execution context.
 A given thread will have its own stack, and CPU registers. However global state, as well
 as values allocated on the heap, will be shared and accessible to all threads in the system
-(See the Synchronization chapter for functions to help with data sharing between different threads.)

+(See the Synchronization chapter for functions to help with data sharing between different threads.)

 
Multiple threads can be thought of as running concurrently, even though
 they might not actually do so.

 
I/O operations that block (i.e. wait for completion) will block the
@@ -314,8 +314,8 @@ It also has the effect of blocking execution in the caller until thr ha
 to provide a name for the thread. This may change how the thread is represented
 in debuggers. Not all platforms support setting the thread name.

 
See Also

-
Synchronization,
-Asynchronous Operations

+
Synchronization,
+Asynchronous Operations