From 2bb57ac57ace37203c505ff17147210feca34d73 Mon Sep 17 00:00:00 2001
From: Martin Sustrik <sustrik@fastmq.commkdir>
Date: Fri, 15 Jan 2010 14:11:39 +0100
Subject: ZMQII-39: Implement IPC transport

---
 man/man7/zmq.7        |  3 +++
 man/man7/zmq_inproc.7 |  3 ++-
 man/man7/zmq_ipc.7    | 34 ++++++++++++++++++++++++++++++++++
 man/man7/zmq_pgm.7    |  1 +
 man/man7/zmq_tcp.7    |  1 +
 man/man7/zmq_udp.7    |  1 +
 6 files changed, 42 insertions(+), 1 deletion(-)
 create mode 100644 man/man7/zmq_ipc.7

(limited to 'man/man7')

diff --git a/man/man7/zmq.7 b/man/man7/zmq.7
index 740726c..61543a7 100644
--- a/man/man7/zmq.7
+++ b/man/man7/zmq.7
@@ -112,6 +112,9 @@ UDP reliable multicast transport:
 PGM reliable multicast transport:
 .BR zmq_pgm(7)
 
+Inter-process transport:
+.BR zmq_ipc (7)
+
 In-process (inter-thread) transport:
 .BR zmq_inproc(7)
 
diff --git a/man/man7/zmq_inproc.7 b/man/man7/zmq_inproc.7
index bc09f90..0c84641 100644
--- a/man/man7/zmq_inproc.7
+++ b/man/man7/zmq_inproc.7
@@ -3,7 +3,7 @@
 In-process (inter-thread) tranport for 0MQ
 .SH SYNOPSIS
 
-In-process transport is optimised for passing messages betweem threads in the
+In-process transport is optimised for passing messages between threads in the
 same process.
 
 Messages are passed directly from one application thread to
@@ -32,6 +32,7 @@ wire format specification.
 
 .SH "SEE ALSO"
 
+.BR zmq_ipc (7)
 .BR zmq_tcp (7)
 .BR zmq_udp (7)
 .BR zmq_pgm (7)
diff --git a/man/man7/zmq_ipc.7 b/man/man7/zmq_ipc.7
new file mode 100644
index 0000000..28e57d0
--- /dev/null
+++ b/man/man7/zmq_ipc.7
@@ -0,0 +1,34 @@
+.TH zmq_ipc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
+.SH NAME
+Inter-process tranport for 0MQ
+.SH SYNOPSIS
+
+In-process transport is optimised for passing messages between processes on the
+same physical machine.
+
+.SH CONNECTION STRING
+
+Connection string for inproc transport is "inproc://" followed by a file name.
+The file will be used as placeholder for a message endpoint. (UNIX domain
+sockets associate a file with the listening socket in a similar way.)
+
+.nf
+    ipc:///tmp/my_ipc_endpoint
+    ipc:///tmp/prices.ipc
+.fi
+
+.SH WIRE FORMAT
+
+IPC transport doesn't transfer messages across the network thus there is no need
+for a wire format specification.
+
+.SH "SEE ALSO"
+
+.BR zmq_inproc (7)
+.BR zmq_tcp (7)
+.BR zmq_udp (7)
+.BR zmq_pgm (7)
+
+.SH AUTHOR
+Martin Sustrik <sustrik at 250bpm dot com>
+
diff --git a/man/man7/zmq_pgm.7 b/man/man7/zmq_pgm.7
index 68af978..39f639b 100644
--- a/man/man7/zmq_pgm.7
+++ b/man/man7/zmq_pgm.7
@@ -80,6 +80,7 @@ Following example shows how messages are arranged in subsequent packets:
 
 .BR zmq_udp (7)
 .BR zmq_tcp (7)
+.BR zmq_ipc (7)
 .BR zmq_inproc (7)
 .BR zmq_setsockopt (3)
 
diff --git a/man/man7/zmq_tcp.7 b/man/man7/zmq_tcp.7
index f5504c8..41a116b 100644
--- a/man/man7/zmq_tcp.7
+++ b/man/man7/zmq_tcp.7
@@ -72,6 +72,7 @@ Binary layout of a larger message:
 
 .BR zmq_udp (7)
 .BR zmq_pgm (7)
+.BR zmq_ipc (7)
 .BR zmq_inproc (7)
 
 .SH AUTHOR
diff --git a/man/man7/zmq_udp.7 b/man/man7/zmq_udp.7
index 151a6d4..d0bf46c 100644
--- a/man/man7/zmq_udp.7
+++ b/man/man7/zmq_udp.7
@@ -37,6 +37,7 @@ Same as with PGM transport except for UDP packet headers.
 
 .BR zmq_pgm (7)
 .BR zmq_tcp (7)
+.BR zmq_ipc (7)
 .BR zmq_inproc (7)
 
 .SH AUTHOR
-- 
cgit v1.2.3