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.
The inproc transport is generally built-in to the nng core, so no extra steps to use it should be necessary.
This transport uses URIs using the scheme
inproc://, followed by
an arbitrary string of text, terminated by a
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.
The inproc transport has no special options.
While inproc accepts the option
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.