From 8ff1ed986dc8fe086c317bca8e6d3c5450e56da3 Mon Sep 17 00:00:00 2001 From: gdamore Date: Sun, 5 Jan 2025 02:33:35 +0000 Subject: deploy: f77e5a5ec7f8b1373eeda0ea56f47137daf40330 --- ref/migrate/nng1.html | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'ref/migrate/nng1.html') diff --git a/ref/migrate/nng1.html b/ref/migrate/nng1.html index 493c85c7..636a19b5 100644 --- a/ref/migrate/nng1.html +++ b/ref/migrate/nng1.html @@ -298,12 +298,13 @@ This was implemented mostly to aid legacy nanomsg applications, and it was both suboptimal in terms of performance.

Modern code should use one of nng_sendmsg, nng_recvmsg, nng_socket_send, or nng_socket_recv 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

+

Error Code Changes

When an operation fails with NNG_ESTOPPED, it means that the associated [nni_aio] object has been permanently stopped and must not be reused. Applications must watch for this error code, and not resubmit an operation that returns it. This is particularly important for callbacks that automatically resubmit operations. Failure to observe this rule will lead to an infinite loop as any further operations on the object will fail immediately with NNG_ESTOPPED.

+

The error codes NNG_EAMBIGUOUS and NNG_ENOARG have been removed.

AIO Provider API changes

The API used for providers for asynchronous I/O operations has changed slightly.