From edd3b6bc34f211bd3d58642d0c69ce1b5bb9dc3b Mon Sep 17 00:00:00 2001 From: gdamore Date: Thu, 9 Oct 2025 01:22:20 +0000 Subject: deploy: 9c834956456924df7c885ab8b79573721acaff5c --- ref/tran/udp.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) (limited to 'ref/tran/udp.html') diff --git a/ref/tran/udp.html b/ref/tran/udp.html index 92674ff8..fc474ed1 100644 --- a/ref/tran/udp.html +++ b/ref/tran/udp.html @@ -301,19 +301,19 @@ and could be used to listen to port 9999 on the host:

  • udp://:9999

    • Socket Address

    -

    When using an nng_sockaddr structure, +

    When using an nng_sockaddr structure, the actual structure is either of type -nng_sockaddr_in (for IPv4) or -nng_sockaddr_in6 (for IPv6).

    +nng_sockaddr_in (for IPv4) or +nng_sockaddr_in6 (for IPv6).

    Transport Options

    The following transport options are supported by this transport, where supported by the underlying platform.

    - - - + + + - +
    OptionTypeDescription
    NNG_OPT_LOCADDRnng_sockaddrThe locally bound address, will be either nng_sockaddr_in or nng_sockaddr_in6.
    NNG_OPT_REMADDRnng_sockaddrThe remote peer address, will be either nng_sockaddr_in or nng_sockaddr_in6. Only valid for pipe and dialer objects.
    NNG_OPT_RECVMAXSZsize_tMaximum size of incoming messages, will be limited to at most 65000.
    NNG_OPT_LOCADDRnng_sockaddrThe locally bound address, will be either nng_sockaddr_in or nng_sockaddr_in6.
    NNG_OPT_REMADDRnng_sockaddrThe remote peer address, will be either nng_sockaddr_in or nng_sockaddr_in6. Only valid for pipe and dialer objects.
    NNG_OPT_RECVMAXSZsize_tMaximum size of incoming messages, will be limited to at most 65000.
    NNG_OPT_UDP_COPY_MAXsize_tThreshold above which received messages are “loaned” up, rather than a new message being allocated and copied into.
    NNG_OPT_UDP_BOUND_PORTintThe locally bound UDP port number (1-65535), read-only for listener objects only.
    NNG_OPT_UDP_BOUND_PORTintThe locally bound UDP port number (1-65535), read-only for listener objects only.

    Maximum Message Size

    @@ -334,7 +334,7 @@ the final user accessible payload will be 1140 bytes. Thus this can be likely be as a safe maximum to employ for SP payload data across all transports.

    The maximum message size is negotiated as part of establishing a peering relationship, and oversize messages will be dropped by the sender before going to the network.

    -

    The maximum message size to receive can be configured with the NNG_OPT_RECVMAXSZ option.

    +

    The maximum message size to receive can be configured with the NNG_OPT_RECVMAXSZ option.

    Keep Alive

    This transports maintains a logical “connection” with each peer, to provide a rough facsimile of a connection based semantic. This requires some resource on each peer. -- cgit v1.2.3-70-g09d2