libzmq/doc/zmq_inproc.adoc

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

82 lines
2.6 KiB
Plaintext
Raw Normal View History

= zmq_inproc(7)
2010-01-13 15:15:01 +01:00
2010-02-10 16:18:46 +01:00
== NAME
2010-03-09 18:47:31 +01:00
zmq_inproc - 0MQ local in-process (inter-thread) communication transport
2010-02-10 16:18:46 +01:00
== SYNOPSIS
2010-03-09 18:47:31 +01:00
The in-process transport passes messages via memory directly between threads
sharing a single 0MQ 'context'.
2010-01-13 15:15:01 +01:00
2010-03-09 18:47:31 +01:00
NOTE: No I/O threads are involved in passing messages using the 'inproc'
transport. Therefore, if you are using a 0MQ 'context' for in-process messaging
only you can initialise the 'context' with zero I/O threads. See
xref:zmq_init.adoc[zmq_init] for details.
2010-01-13 15:15:01 +01:00
== ADDRESSING
2012-10-27 02:43:19 +02:00
A 0MQ endpoint is a string consisting of a 'transport'`://` followed by an
'address'. The 'transport' specifies the underlying protocol to use. The
'address' specifies the transport-specific address to connect to.
For the in-process transport, the transport is `inproc`, and the meaning of
the 'address' part is defined below.
2010-03-09 18:47:31 +01:00
Assigning a local address to a socket
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
When assigning a local address to a 'socket' using _zmq_bind()_ with the
'inproc' transport, the 'endpoint' shall be interpreted as an arbitrary string
identifying the 'name' to create. The 'name' must be unique within the 0MQ
'context' associated with the 'socket' and may be up to 256 characters in
length. No other restrictions are placed on the format of the 'name'.
2010-01-13 15:15:01 +01:00
2010-03-09 18:47:31 +01:00
Connecting a socket
~~~~~~~~~~~~~~~~~~~
When connecting a 'socket' to a peer address using _zmq_connect()_ with the
'inproc' transport, the 'endpoint' shall be interpreted as an arbitrary string
identifying the 'name' to connect to. Before version 4.0 he 'name' must have
been previously created by assigning it to at least one 'socket' within the
same 0MQ 'context' as the 'socket' being connected. Since version 4.0 the
order of _zmq_bind()_ and _zmq_connect()_ does not matter just like for the tcp
transport type.
2010-01-13 15:15:01 +01:00
== EXAMPLES
2010-03-09 18:47:31 +01:00
.Assigning a local address to a socket
----
2012-10-27 02:43:19 +02:00
// Assign the in-process name "#1"
2010-03-09 18:47:31 +01:00
rc = zmq_bind(socket, "inproc://#1");
assert (rc == 0);
2012-10-27 02:43:19 +02:00
// Assign the in-process name "my-endpoint"
2010-03-09 18:47:31 +01:00
rc = zmq_bind(socket, "inproc://my-endpoint");
assert (rc == 0);
----
.Connecting a socket
----
2012-10-27 02:43:19 +02:00
// Connect to the in-process name "#1"
2010-03-09 18:47:31 +01:00
rc = zmq_connect(socket, "inproc://#1");
assert (rc == 0);
2012-10-27 02:43:19 +02:00
// Connect to the in-process name "my-endpoint"
2010-03-09 18:47:31 +01:00
rc = zmq_connect(socket, "inproc://my-endpoint");
assert (rc == 0);
----
2010-01-13 15:15:01 +01:00
== SEE ALSO
* xref:zmq_bind.adoc[zmq_bind]
* xref:zmq_connect.adoc[zmq_connect]
* xref:zmq_ipc.adoc[zmq_ipc]
* xref:zmq_tcp.adoc[zmq_tcp]
* xref:zmq_pgm.adoc[zmq_pgm]
* xref:zmq_vmci.adoc[zmq_vmci]
* xref:zmq.adoc[zmq]
2010-01-13 15:15:01 +01:00
2009-12-03 12:58:16 +01:00
== AUTHORS
This page was written by the 0MQ community. To make a change please
read the 0MQ Contribution Policy at <https://zeromq.org/how-to-contribute/>.