From d04b0cfcb5a37f5b6b6ba0fbd031bdbad94399b1 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Tue, 27 Nov 2018 16:27:20 -0800 Subject: fixes #680 Public TCP API --- docs/man/nng_tcp.5.adoc | 69 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 69 insertions(+) create mode 100644 docs/man/nng_tcp.5.adoc (limited to 'docs/man/nng_tcp.5.adoc') diff --git a/docs/man/nng_tcp.5.adoc b/docs/man/nng_tcp.5.adoc new file mode 100644 index 00000000..10a3c2f3 --- /dev/null +++ b/docs/man/nng_tcp.5.adoc @@ -0,0 +1,69 @@ += nng_tcp(5) +// +// Copyright 2018 Staysail Systems, Inc. +// Copyright 2018 Capitar IT Group BV +// +// This document is supplied under the terms of the MIT License, a +// copy of which should be located in the distribution where this +// file was obtained (LICENSE.txt). A copy of the license may also be +// found online at https://opensource.org/licenses/MIT. +// + +== NAME + +nng_tcp - TCP connection + +== SYNOPSIS + +[source, c] +---- +#include +#include + +typedef struct nng_tcp_s nng_tcp; +---- + +== DESCRIPTION + +An `nng_tcp` (((TCP connection))) represents a connected stream. +TCP stream objects can be used to send or receive data. + +NOTE: The `nng_tcp` object is used for raw TCP connections, and +should not be confused with a pipe object created using the +<> transport. + +TIP: Most NNG applications should not use this, but instead use the +`<>` transport instead. + +These objects are created either establishing an outgoing connection +with `<>` or by +accepting in incoming connection with +`<>`. + +TCP connections are byte streams, and are "`reliable`" in that data +will not be delivered out of order, or with portions missing. + +Data can be sent using `<>` or +received with `<>`. + +When the connection is no longer needed, it should be freed with +`<>`. + +TIP: It is possible to close the connection, without freeing it, by +using `<>`. + +== SEE ALSO + +[.text-left] +<>, +<>, +<>, +<>, +<>, +<>, +<>, +<>, +<>, +<>, +<>, +<> -- cgit v1.2.3-70-g09d2