From bb67a9767078bd98add53ead0e0e2f1390cfb539 Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 2 Jan 2025 03:17:48 +0000 Subject: deploy: f7bf24f429cbc488b861ab1b1e4cf1983af56295 --- ref/migrate/nng1.html | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'ref/migrate/nng1.html') diff --git a/ref/migrate/nng1.html b/ref/migrate/nng1.html index 925351a6..c990595a 100644 --- a/ref/migrate/nng1.html +++ b/ref/migrate/nng1.html @@ -251,6 +251,12 @@ in your compilation environment.

be supplied should avoid surprises later as new versions of protocols are added.)

Additionally, the header files for protocols are now empty, as all of their content has been moved to nng/nng.h. Please remove #include references to protocol headers as we anticipate removing them in the future.

+

NNG_FLAG_ALLOC Removed

+

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. +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 been permanently stopped and must not be reused. Applications must watch for this error code, and -- cgit v1.2.3-70-g09d2