From c4b4b89e95f3c6bc701a32aba9884ceb3aa118b2 Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 2 Jan 2025 03:46:39 +0000 Subject: deploy: f293e96b03b22c6a91140b118c4e15059e285543 --- ref/api/sock.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'ref/api/sock.html') diff --git a/ref/api/sock.html b/ref/api/sock.html index 215726e0..cdb4b824 100644 --- a/ref/api/sock.html +++ b/ref/api/sock.html @@ -485,7 +485,7 @@ Failure to do so will leak the memory.

This is the preferred function to use for receiving data on a socket. While it does require a few extra steps on the part of the application, the lowest latencies and highest performance will be achieved by using -this function instead of nng_recv or nng_recvmsg.

+this function instead of nng_recv or nng_recvmsg.

Polling Socket Events

int nng_socket_get_recv_poll_fd(nng_socket s, int *fdp);
@@ -586,7 +586,7 @@ int main(int argc, char **argv) {
 }

Example 3: Watching a Periodic Timestamp

-

This example demonstrates the use of nng_aio, [nng_recv_aio], to build a client to +

This example demonstrates the use of nng_aio, nng_recv_aio, to build a client to watch for messages received from the service created in Example 2. Error handling is elided for the sake of clarity.

#include <stdlib.h>
@@ -645,7 +645,7 @@ int main(int argc, char **argv) {
                                 
                             
 
-                            
 
@@ -659,7 +659,7 @@ int main(int argc, char **argv) {
                         
                     
 
-                    
             
-- 
cgit v1.2.3-70-g09d2