2010-02-10 16:18:46 +01:00
|
|
|
zmq_ipc(7)
|
|
|
|
|
==========
|
2010-01-15 14:11:39 +01:00
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
|
|
|
|
|
NAME
|
|
|
|
|
----
|
|
|
|
|
zmq_ipc - 0MQ transport to pass messages between processes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
|
--------
|
2010-01-18 13:16:14 +01:00
|
|
|
Inter-process transport is optimised for passing messages between processes on
|
|
|
|
|
the same physical machine.
|
2010-01-15 14:11:39 +01:00
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
CONNECTION STRING
|
|
|
|
|
-----------------
|
2010-02-21 16:58:53 +01:00
|
|
|
Connection string for inter-process transport is "ipc://" followed by a file
|
|
|
|
|
name. The file will be used as placeholder for a message endpoint. (UNIX domain
|
2010-01-15 14:11:39 +01:00
|
|
|
sockets associate a file with the listening socket in a similar way.)
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
----
|
2010-01-15 14:11:39 +01:00
|
|
|
ipc:///tmp/my_ipc_endpoint
|
|
|
|
|
ipc:///tmp/prices.ipc
|
2010-02-10 16:18:46 +01:00
|
|
|
----
|
2010-01-15 14:11:39 +01:00
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
WIRE FORMAT
|
|
|
|
|
-----------
|
2010-01-15 14:11:39 +01:00
|
|
|
IPC transport doesn't transfer messages across the network thus there is no need
|
|
|
|
|
for a wire format specification.
|
|
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
SEE ALSO
|
|
|
|
|
--------
|
|
|
|
|
linkzmq:zmq_inproc[7]
|
|
|
|
|
linkzmq:zmq_tcp[7]
|
|
|
|
|
linkzmq:zmq_udp[7]
|
|
|
|
|
linkzmq:zmq_pgm[7]
|
2010-01-15 14:11:39 +01:00
|
|
|
|
|
|
|
|
|
2010-02-10 16:18:46 +01:00
|
|
|
AUTHOR
|
|
|
|
|
------
|
|
|
|
|
Martin Sustrik <sustrik at 250bpm dot com>
|
