From 131726d96414aa1a35e8319db0785221e1230566 Mon Sep 17 00:00:00 2001 From: gdamore Date: Fri, 10 Jan 2025 07:46:01 +0000 Subject: deploy: 73f50e2679525e7df8734c875a3c12732565f953 --- ref/migrate/nanomsg.html | 1 + ref/migrate/nng1.html | 16 ++++++++++++---- 2 files changed, 13 insertions(+), 4 deletions(-) (limited to 'ref/migrate') diff --git a/ref/migrate/nanomsg.html b/ref/migrate/nanomsg.html index bed90b48..4f0a5207 100644 --- a/ref/migrate/nanomsg.html +++ b/ref/migrate/nanomsg.html @@ -331,6 +331,7 @@ using nn_dial inside the URL is not present in NNG. The correct way to specify the local address is using the NNG_OPT_LOCADDR option on the dialer before starting to dial.

+ diff --git a/ref/migrate/nng1.html b/ref/migrate/nng1.html index 636a19b5..ceac557d 100644 --- a/ref/migrate/nng1.html +++ b/ref/migrate/nng1.html @@ -331,10 +331,6 @@ can be simply removed from your application:

Additionally, the header files containing these functions have been removed, such as nng/transport/ipc/ipc.h. Simply remove #include references to those files.

-

The NNG_OPT_WSS_REQUEST_HEADERS and NNG_OPT_WSS_RESPONSE_HEADERS aliases for -NNG_OPT_WS_OPT_WS_REQUEST_HEADERS and NNG_OPT_WS_RESPONSE_HEADERS have been removed. -Just convert any use of them to NNG_OPT_WS_REQUEST_HEADERS or -NNG_OPT_WS_RESPONSE_HEADERS as appropriate.

TLS Configuration

The support for configuring TLS via NNG_OPT_TLS_CONFIG, NNG_TLS_AUTH_MODE, NNG_OPT_TLS_CA_FILE, NNG_OPT_TLS_SERVER_NAME, and similar has been removed.

@@ -497,6 +493,8 @@ accessors functions are provided:

  • u_rawurl is removed - a “cooked” URL can be obtained from the new nng_url_sprintf function.

    • HTTP API

    +

    The entire HTTP API has been refactored and should be much simpler to use and more efficient. +Applications directly using the HTTP API will need to be fully modified.

    A few limits on string lengths of certain values are now applied, which allows us to preallocate values and eliminate certain unreasonable error paths. If values longer than these are supplied in certain APIs they may be silently truncated to the limit:

    @@ -520,6 +518,15 @@ They may silently truncate data.

    The HTTP handler objects may not be modified once in use. Previously this would fail with NNG_EBUSY. These checks are removed now, but debug builds will assert if an application tries to do so.

    +

    WebSocket API

    +

    The NNG_OPT_WSS_REQUEST_HEADERS, NNG_OPT_WSS_RESPONSE_HEADERS and +NNG_OPT_WS_OPT_WS_REQUEST_HEADERS, NNG_OPT_WS_RESPONSE_HEADERS have been removed.

    +

    The NNG_OPT_WS_REQUEST_HEADER and NNG_OPT_WS_RESPONSE_HEADER option prefixes have been +collapsed into just NNG_OPT_WS_HEADER, with slightly different semantics. It still is +a prefix (append the name of the header of interest), but setting it can only affect +outbound headers (request header for dialers, response header for listeners), and when +reading it on a pipe, the value returned is the header sent by the remote peer.

    +

    The undocumented hook function signature has changed to reflect changes in the HTTP API.

    Security Descriptors (Windows Only)

    The NNG_OPT_IPC_SECURITY_DESCRIPTOR option is removed, and replaced with the functions [nng_listener_get_security_descriptor] and @@ -537,6 +544,7 @@ See nng_args_parse + -- cgit v1.2.3-70-g09d2