summaryrefslogtreecommitdiff
path: root/man/man7/zmq_inproc.7
diff options
context:
space:
mode:
authorMartin Sustrik <sustrik@fastmq.commkdir>2010-01-13 15:15:01 +0100
committerMartin Sustrik <sustrik@fastmq.commkdir>2010-01-13 15:15:01 +0100
commit06105d164230800e8ea42ddd513e2f7fb27e6f2f (patch)
treed9d31f25f839b9b8d1ea720338d7f9fbda7fbbff /man/man7/zmq_inproc.7
parent30a107e06d48ebbc7a635ba4fb21a24e385cf4e4 (diff)
transports man pages updated
Diffstat (limited to 'man/man7/zmq_inproc.7')
-rw-r--r--man/man7/zmq_inproc.734
1 files changed, 33 insertions, 1 deletions
diff --git a/man/man7/zmq_inproc.7 b/man/man7/zmq_inproc.7
index 7f43ca7..bc09f90 100644
--- a/man/man7/zmq_inproc.7
+++ b/man/man7/zmq_inproc.7
@@ -2,8 +2,40 @@
.SH NAME
In-process (inter-thread) tranport for 0MQ
.SH SYNOPSIS
-.SH DESCRIPTION
+
+In-process transport is optimised for passing messages betweem threads in the
+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
+the library (
+.IR zmq_init
+) with zero I/O worker threads.
+
+.SH CONNECTION STRING
+
+Connection string for inproc transport is "inproc://" followed by an arbitrary
+string. There are no restrictions on the string format:
+
+.nf
+ inproc://my_endpoint
+ inproc://feeds/opra/cboe
+ inproc://feeds.opra.nasdaq
+ inproc://!&W#($)_@_123*((^^^
+.fi
+
+.SH WIRE FORMAT
+
+In-process transport transfers messages via memory thus there is no need for a
+wire format specification.
+
.SH "SEE ALSO"
+
+.BR zmq_tcp (7)
+.BR zmq_udp (7)
+.BR zmq_pgm (7)
+
.SH AUTHOR
Martin Sustrik <sustrik at 250bpm dot com>