From c4b4b89e95f3c6bc701a32aba9884ceb3aa118b2 Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 2 Jan 2025 03:46:39 +0000 Subject: deploy: f293e96b03b22c6a91140b118c4e15059e285543 --- ref/migrate/nng1.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'ref/migrate/nng1.html') diff --git a/ref/migrate/nng1.html b/ref/migrate/nng1.html index c990595a..de0a0297 100644 --- a/ref/migrate/nng1.html +++ b/ref/migrate/nng1.html @@ -255,7 +255,7 @@ Please remove #include references to protocol headers as we anticip

The NNG_FLAG_ALLOC flag that allowed a zero copy semantic with nng_send and nng_recv is removed. This was implemented mostly to aid legacy nanomsg applications, and it was both error prone and still a bit suboptimal in terms of performance.

-

Modern code should use one of nng_sendmsg, nng_recvmsg, nng_send_aio, or [nng_recv_aio] to get the maximum performance benefit. +

Modern code should use one of nng_sendmsg, nng_recvmsg, nng_send_aio, or nng_recv_aio to get the maximum performance benefit. Working directly with nng_msg structures gives more control, reduces copies, and reduces allocation activity.

New AIO Error Code NNG_ESTOPPED

When an operation fails with NNG_ESTOPPED, it means that the associated [nni_aio] object has -- cgit v1.2.3-70-g09d2