From e65ecddd1c04ab5b784b0919e62bc87d2a750ef6 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Thu, 23 Jan 2020 23:53:54 -0800 Subject: Publishing updates for v1.2 --- man/v1.2/nng_stream_close.3str.html | 520 ++---------------------------------- 1 file changed, 17 insertions(+), 503 deletions(-) (limited to 'man/v1.2/nng_stream_close.3str.html') diff --git a/man/v1.2/nng_stream_close.3str.html b/man/v1.2/nng_stream_close.3str.html index 648f3664..48a3b9bf 100644 --- a/man/v1.2/nng_stream_close.3str.html +++ b/man/v1.2/nng_stream_close.3str.html @@ -1,505 +1,18 @@ --- -version: 1.2 +version: v1.2 layout: refman --- - + - + nng_stream_close(3str) - - - + + -

NAME

+

NAME

nng_stream_close - close byte stream

@@ -537,13 +50,13 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b

The nng_stream_close() function closes the -byte stream s.

+byte stream s.

If any operations are pending, such as -nng_stream_send() +nng_stream_send() or -nng_stream_recv(), +nng_stream_recv(), they will be terminated with an NNG_ECLOSED error condition. Also, any new operations will fail with NNG_ECLOSED after the connection @@ -574,7 +87,7 @@ have completely transmitted. Closing the connection does not free the resources associated with it. Once it is certain that no more operations are pending on the connection, it should be freed with -nng_stream_free(). +nng_stream_free(). @@ -601,14 +114,15 @@ it should be freed with

SEE ALSO

-

nng_strerror(3), -nng_stream_free(3str), -nng_stream_recv(3str), -nng_stream_send(3str), -nng_stream(5)

+

nng_strerror(3), +nng_stream_free(3str), +nng_stream_recv(3str), +nng_stream_send(3str), +nng_stream(5)

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