= nng_ipc(5) // // Copyright 2018 Staysail Systems, Inc. // Copyright 2018 Capitar IT Group BV // Copyright 2019 Devolutions // // 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_ipc - IPC connection == SYNOPSIS [source, c] ---- #include #include typedef struct nng_ipc_s nng_ipc; ---- == DESCRIPTION An `nng_ipc` (((IPC connection))) represents a connected stream using interprocess communication (IPC). IPC stream objects can be used to send or receive data. NOTE: The `nng_ipc` object is used for raw IPC 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 <>. IPC 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 <>. === Options The following options are applicable to IPC connections, and may be accessed using the <> and <> functions. * <> * <> * <> * <> * <> * <> Other platform specific options may be available as well. == SEE ALSO [.text-left] <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>, <>