zmq_term(3) [debian man page]

ZMQ_TERM(3)							    0MQ Manual							       ZMQ_TERM(3)

NAME

       zmq_term - terminate 0MQ context

SYNOPSIS

       int zmq_term (void *context);

DESCRIPTION

       The zmq_term() function shall terminate the 0MQ context context.

       Context termination is performed in the following steps:

	1. Any blocking operations currently in progress on sockets open within context shall return immediately with an error code of ETERM. With
	   the exception of zmq_close(), any further operations on sockets open within context shall fail with an error code of ETERM.

	2. After interrupting all blocking calls, zmq_term() shall block until the following conditions are satisfied:

	   o   All sockets open within context have been closed with zmq_close().

	   o   For each socket within context, all messages sent by the application with zmq_send() have either been physically transferred to a
	       network peer, or the socket's linger period set with the ZMQ_LINGER socket option has expired.

       For further details regarding socket linger behaviour refer to the ZMQ_LINGER option in zmq_setsockopt(3).

RETURN VALUE

       The zmq_term() function shall return zero if successful. Otherwise it shall return -1 and set errno to one of the values defined below.

ERRORS

       EFAULT
	   The provided context was invalid.

       EINTR
	   Termination was interrupted by a signal. It can be restarted if needed.

SEE ALSO

       zmq(7) zmq_init(3) zmq_close(3) zmq_setsockopt(3)

AUTHORS

       This manual page was written by the 0MQ community.

0MQ 2.2.0							    04/04/2012							       ZMQ_TERM(3)

ZMQ_INPROC(7)							    0MQ Manual							     ZMQ_INPROC(7)

NAME

       zmq_inproc - 0MQ local in-process (inter-thread) communication transport

SYNOPSIS

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

	   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 zmq_init(3) for details.

ADDRESSING

       A 0MQ 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 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.

   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 0MQ 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

       This manual page was written by the 0MQ community.

0MQ 2.2.0							    04/04/2012							     ZMQ_INPROC(7)