nng_ctx_send(3)

The nng_ctx_send() sends a message using the -context ctx asynchronously.

The nng_ctx_send() sends a message using the +context ctx asynchronously.

The message to send must have previously been set on the aio -using the nng_aio_set_msg() function. +using the nng_aio_set_msg() function. The function assumes “ownership” of the message.

If the message was successfully queued for delivery to the socket, -then the aio will be completed, and nng_aio_result() +then the aio will be completed, and nng_aio_result() will return zero. In this case the socket will dispose of the message when it is finished with it.

@@ -570,12 +83,12 @@ socket, or in flight over physical media.

If the operation fails for any reason (including cancellation or timeout), then the aio callback will be executed and -nng_aio_result() will return a non-zero error status. +nng_aio_result() will return a non-zero error status. In this case, the callback has a responsibility to retrieve the message from -the aio with nng_aio_get_msg() and dispose of +the aio with nng_aio_get_msg() and dispose of it appropriately. (This may include retrying the send operation on the same or a different -socket, or deallocating the message with nng_msg_free().)

+socket, or deallocating the message with nng_msg_free().)

@@ -600,7 +113,7 @@ protocol, so examination of the protocol documentation is encouraged. Context send operations are asynchronous. If a synchronous operation is needed, one can be constructed by using a NULL callback on the aio and then waiting for the operation using -nng_aio_wait(). +nng_aio_wait().

@@ -684,17 +197,18 @@ If a synchronous operation is needed, one can be constructed by using a

NAME

NAME

DESCRIPTION

SEE ALSO