From 8b8fdbdc2e3fef03e21177eb3710491e4c080d43 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Thu, 23 Jan 2020 23:24:04 -0800 Subject: Publishing updates for v1.2.4 --- man/v1.2.4/nng_aio_stop.3.html | 129 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) create mode 100644 man/v1.2.4/nng_aio_stop.3.html (limited to 'man/v1.2.4/nng_aio_stop.3.html') diff --git a/man/v1.2.4/nng_aio_stop.3.html b/man/v1.2.4/nng_aio_stop.3.html new file mode 100644 index 00000000..1d5126a3 --- /dev/null +++ b/man/v1.2.4/nng_aio_stop.3.html @@ -0,0 +1,129 @@ +--- +version: v1.2.4 +layout: refman +--- + + + + + + + +nng_aio_stop(3) + + + + + + +
+
+

SYNOPSIS

+
+
+
+
#include <nng/nng.h>
+
+void nng_aio_stop(nng_aio *aio);
+
+
+
+
+
+

DESCRIPTION

+
+
+

The nng_aio_stop() function stops the asynchronous I/O operation +associated with aio by aborting with NNG_ECANCELED, and then waits +for it to complete or to be completely aborted.

+
+
+

If an operation is in progress when this function is called, that operation +is canceled and the callback function is not allowed to run.

+
+
+

If the callback function is already running when this function is called, +then it is allowed to complete before returning to the caller.

+
+
+

No new operations will be started on this aio.

+
+
+ + + + + +
+ + +Calling this function means that the operation may be aborted without +completing its callback function. +
+
+
+ + + + + +
+ + +When multiple asynchronous I/O handles are in use and need to be +shut down, it is safest to stop all of them, before deallocating any of +this with nng_aio_free(), particularly if the callbacks +might attempt to reschedule additional operations. +
+
+
+
+
+

RETURN VALUES

+
+
+

None.

+
+
+
+
+

ERRORS

+
+
+

None.

+
+
+
+
+

SEE ALSO

+
+
+

nng_aio_cancel(3), +nng_aio_free(3), +nng_aio_wait(3), +nng_aio_alloc(3), +nng_aio(5), +nng(7)

+
+
+
+
+ + + \ No newline at end of file -- cgit v1.2.3-70-g09d2