加入 Gitee

与超过 1200万开发者一起发现、参与优秀开源项目，私有仓库也完全免费：）

克隆/下载

nng_inproc.7.adoc 2.14 KB

= nng_inproc(7)
//
// Copyright 2019 Staysail Systems, Inc. <info@staysail.tech>
// Copyright 2018 Capitar IT Group BV <info@capitar.com>
//
// 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_inproc - intra-process transport

== SYNOPSIS

[source,c]
----
#include <nng/transport/inproc/inproc.h>

int nng_inproc_register(void);
----

== DESCRIPTION

(((transport, _inproc_)))
(((intra-process)))
The ((_inproc_ transport)) provides communication support between
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

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

=== URI Format
(((URI, `inproc://`)))
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 xref:nng_sockaddr.5.adoc[`nng_sockaddr`] structure,
the actual structure is of type
xref:nng_sockaddr_inproc.5.adoc[`nng_sockaddr_inproc`].

=== Transport Options

The _inproc_ transport has no special options.

NOTE: While _inproc_ accepts the option
xref:nng_options.5.adoc#NNG_OPT_RECVMAXSZ[`NNG_OPT_RECVMAXSZ`] for
compatibility, the value of the option is ignored with no enforcement.
As _inproc_ peers are in the same address space, they are implicitly trusted,
and thus it makes no sense to spend cycles protecting a program from itself.

== SEE ALSO

[.text-left]
xref:nng_inproc_register.3.adoc[nng_inproc_register(3)],
xref:nng_sockaddr_inproc.5.adoc[nng_sockaddr_inproc(5)],
xref:nng.7.adoc[nng(7)]

一键复制编辑原始数据按行查看历史

提交于 2020-06-18 20:31 . Harmonize the use of NNG in documentation.

nng_inproc(7)

NAME

nng_inproc - intra-process transport

SYNOPSIS

#include <nng/transport/inproc/inproc.h>

int nng_inproc_register(void);

DESCRIPTION

The inproc transport provides communication support between 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

This transport is generally built-in to the 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.

Note	While inproc accepts the option `NNG_OPT_RECVMAXSZ` for compatibility, the value of the option is ignored with no enforcement. As inproc peers are in the same address space, they are implicitly trusted, and thus it makes no sense to spend cycles protecting a program from itself.

SEE ALSO

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

马建仓 AI 助手

尝试更多

代码解读

代码找茬

代码优化

1

https://gitee.com/chenlh_kwick/nng.git

git@gitee.com:chenlh_kwick/nng.git

chenlh_kwick

nng

nng

master