#include <nng/transport/ipc/ipc.h> int nng_ipc_register(void);
|This documentation is for the TIP (development tree) of NNG and may represent unreleased changes or functionality that is experimental, and is subject to change before release. The latest released version is v1.3.2. See the documentation for v1.3.2 for the most up-to-date information.|
nng_ipc - IPC transport
(transport, ipc) The ipc transport provides communication support between sockets within different processes on the same host. For POSIX platforms, this is implemented using UNIX domain sockets. For Windows, this is implemented using Windows Named Pipes. Other platforms may have different implementation strategies.
This transport is generally built-in to the core, so no extra steps to use it should be necessary.
This transport uses URIs using the scheme
ipc://, followed by a path
name in the file system where the socket or named pipe should be created.
On Windows, all names are prefixed by
When using relative paths on POSIX systems, the address used and returned
in properties like
If compatibility with legacy nanomsg applications is required,
then pathnames must not be longer than 122 bytes, including the final
The following transport options are supported by this transport, where supported by the underlying platform.