From 3079d4aa9bbbca02c36dcb7ff6a3f6d24bd21189 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Fri, 9 Nov 2018 19:59:29 -0800 Subject: man page updates for 1.1.0 --- man/v1.1.0/nng_inproc.7.html | 612 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 612 insertions(+) create mode 100644 man/v1.1.0/nng_inproc.7.html (limited to 'man/v1.1.0/nng_inproc.7.html') diff --git a/man/v1.1.0/nng_inproc.7.html b/man/v1.1.0/nng_inproc.7.html new file mode 100644 index 00000000..c4c1a123 --- /dev/null +++ b/man/v1.1.0/nng_inproc.7.html @@ -0,0 +1,612 @@ +--- +version: 1.1.0 +layout: refman +--- + + + + + + + +nng_inproc(7) + + + + + + + +
+
+

SYNOPSIS

+
+
+
+
#include <nng/transport/inproc/inproc.h>
+
+int nng_inproc_register(void);
+
+
+
+
+
+

DESCRIPTION

+
+
+

+ +The inproc transport provides communication support between +nng sockets within the same process. +This may be used as an alternative +to slower transports when data must be moved within the same process.

+
+
+

This transport tries hard to avoid copying data, and thus is very +light-weight.

+
+
+

Registration

+
+

The inproc transport is generally built-in to the nng core, so +no extra steps to use it should be necessary.

+
+
+
+

URI Format

+
+

+This transport uses URIs using the scheme inproc://, followed by +an arbitrary string of text, terminated by a NUL byte.

+
+
+

Multiple URIs can be used within the +same application, and they will not interfere with one another.

+
+
+

Two applications may also use the same URI without interfering with each +other, and they will be unable to communicate with each other using +that URI.

+
+
+
+

Socket Address

+
+

When using an nng_sockaddr structure, +the actual structure is of type +nng_sockaddr_inproc.

+
+
+
+

Transport Options

+
+

The inproc transport has no special options.

+
+
+
+
+
+

SEE ALSO

+
+
+

nng_inproc_register(3), +nng_sockaddr_inproc(5), +nng(7)

+
+
+
+
+ + -- cgit v1.2.3-70-g09d2