From e645fc2693acc796304498909786b7b47005b429 Mon Sep 17 00:00:00 2001 From: Martin Lucina Date: Mon, 23 Jan 2012 08:53:35 +0100 Subject: Imported Upstream version 2.1.3 --- doc/zmq_inproc.html | 669 ---------------------------------------------------- 1 file changed, 669 deletions(-) delete mode 100644 doc/zmq_inproc.html (limited to 'doc/zmq_inproc.html') diff --git a/doc/zmq_inproc.html b/doc/zmq_inproc.html deleted file mode 100644 index 8a3aceb..0000000 --- a/doc/zmq_inproc.html +++ /dev/null @@ -1,669 +0,0 @@ - - - - - -zmq_inproc(7) - - - - - -
-

SYNOPSIS

-
-

The in-process transport passes messages via memory directly between threads -sharing a single ØMQ context.

-
- - - -
-
Note
-		No I/O threads are involved in passing messages using the inproc -transport. Therefore, if you are using a ØMQ context for in-process messaging -only you can initialise the context with zero I/O threads. See -zmq_init(3) for details.
-
-
-

ADDRESSING

-
-

A ØMQ address string consists of two parts as follows: -transport://endpoint. The transport part specifies the underlying -transport protocol to use, and for the in-process transport shall be set to -inproc. The meaning of the endpoint part for the in-process transport is -defined below.

-

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 ØMQ -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.

-

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. The name must have been previously -created by assigning it to at least one socket within the same ØMQ context -as the socket being connected.

-
-

WIRE FORMAT

-
-

Not applicable.

-
-

EXAMPLES

-
-
-
Assigning a local address to a socket
-
-
/* Assign the in-process name "#1" */
-rc = zmq_bind(socket, "inproc://#1");
-assert (rc == 0);
-/* Assign the in-process name "my-endpoint" */
-rc = zmq_bind(socket, "inproc://my-endpoint");
-assert (rc == 0);
-
-
-
Connecting a socket
-
-
/* Connect to the in-process name "#1" */
-rc = zmq_connect(socket, "inproc://#1");
-assert (rc == 0);
-/* Connect to the in-process name "my-endpoint" */
-rc = zmq_connect(socket, "inproc://my-endpoint");
-assert (rc == 0);
-
-
-

SEE ALSO

-
-

zmq_bind(3) -zmq_connect(3) -zmq_ipc(7) -zmq_tcp(7) -zmq_pgm(7) -zmq(7)

-
-

AUTHORS

-
-

The ØMQ documentation was written by Martin Sustrik <sustrik@250bpm.com> and -Martin Lucina <mato@kotelna.sk>.

-
-
-
- - - -- cgit v1.2.3