other versions
- wheezy-backports 3.2.3+dfsg-2~bpo70+1
- jessie 4.0.5+dfsg-2+deb8u1
- testing 4.2.1-4
- unstable 4.2.1-4
ZMQ_IPC(7) | 0MQ Manual | ZMQ_IPC(7) |
NAME¶
zmq_ipc - 0MQ local inter-process communication transportSYNOPSIS¶
The inter-process transport passes messages between local processes using a system-dependent IPC mechanism.ADDRESSING¶
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.Binding a socket¶
When binding a socket to a local address using zmq_bind() with the ipc transport, the endpoint shall be interpreted as an arbitrary string identifying the pathname to create. The pathname must be unique within the operating system namespace used by the ipc implementation, and must fulfill any restrictions placed by the operating system on the format and length of a pathname.Connecting a socket¶
When connecting a socket to a peer address using zmq_connect() with the ipc transport, the endpoint shall be interpreted as an arbitrary string identifying the pathname to connect to. The pathname must have been previously created within the operating system namespace by assigning it to a socket with zmq_bind().EXAMPLES¶
Assigning a local address to a socket.// Assign the pathname "/tmp/feeds/0" rc = zmq_bind(socket, "ipc:///tmp/feeds/0"); assert (rc == 0);
// Connect to the pathname "/tmp/feeds/0" rc = zmq_connect(socket, "ipc:///tmp/feeds/0"); assert (rc == 0);
SEE ALSO¶
zmq_bind(3) zmq_connect(3) zmq_inproc(7) zmq_tcp(7) zmq_pgm(7) zmq_getsockopt(3) zmq(7)AUTHORS¶
This 0MQ manual page was written by Pieter Hintjens < ph@imatix.com[1]>, Martin Sustrik < sustrik@250bpm.com[2]> and Martin Lucina < mato@kotelna.sk[3]>.NOTES¶
- 1.
- ph@imatix.com
mailto:ph@imatix.com
- 2.
- sustrik@250bpm.com
mailto:sustrik@250bpm.com
- 3.
- mato@kotelna.sk
mailto:mato@kotelna.sk
05/02/2013 | 0MQ 3.2.2 |