2010-02-10 16:18:46 +01:00
|
|
|
zmq_inproc(7)
|
|
|
|
|
=============
|
2010-01-13 15:15:01 +01:00
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
zmq_inproc - 0MQ transport to pass messages between threads
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2010-01-15 14:11:39 +01:00
|
|
|
In-process transport is optimised for passing messages between threads in the
|
2010-01-13 15:15:01 +01:00
|
|
|
same process.
|
|
|
|
|
|
|
|
|
|
Messages are passed directly from one application thread to
|
|
|
|
|
another application thread. There are no intervening I/O threads involved.
|
|
|
|
|
Thus, if you are using 0MQ for in-process messaging only, you can initialise
|
2010-02-10 16:18:46 +01:00
|
|
|
the library (linkzmq:zmq_init[3]) with zero I/O worker threads.
|
2010-01-13 15:15:01 +01:00
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
CONNECTION STRING
|
|
|
|
|
-----------------
|
2010-01-13 15:15:01 +01:00
|
|
|
Connection string for inproc transport is "inproc://" followed by an arbitrary
|
|
|
|
|
string. There are no restrictions on the string format:
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
----
|
2010-01-13 15:15:01 +01:00
|
|
|
inproc://my_endpoint
|
|
|
|
|
inproc://feeds/opra/cboe
|
|
|
|
|
inproc://feeds.opra.nasdaq
|
|
|
|
|
inproc://!&W#($)_@_123*((^^^
|
2010-02-10 16:18:46 +01:00
|
|
|
----
|
2010-01-13 15:15:01 +01:00
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
WIRE FORMAT
|
|
|
|
|
-----------
|
2010-01-13 15:15:01 +01:00
|
|
|
In-process transport transfers messages via memory thus there is no need for a
|
|
|
|
|
wire format specification.
|
|
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
linkzmq:zmq_ipc[7]
|
|
|
|
|
linkzmq:zmq_tcp[7]
|
|
|
|
|
linkzmq:zmq_udp[7]
|
|
|
|
|
linkzmq:zmq_pgm[7]
|
2010-01-13 15:15:01 +01:00
|
|
|
|
2009-12-03 12:58:16 +01:00
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
AUTHOR
|
|
|
|
|
------
|
|
|
|
|
Martin Sustrik <sustrik at 250bpm dot com>
|
