summaryrefslogtreecommitdiff
path: root/man/man7/zmq_inproc.7
diff options
context:
space:
mode:
Diffstat (limited to 'man/man7/zmq_inproc.7')
-rw-r--r--man/man7/zmq_inproc.742
1 files changed, 0 insertions, 42 deletions
diff --git a/man/man7/zmq_inproc.7 b/man/man7/zmq_inproc.7
deleted file mode 100644
index 279d9b5..0000000
--- a/man/man7/zmq_inproc.7
+++ /dev/null
@@ -1,42 +0,0 @@
-.TH zmq_inproc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
-.SH NAME
-0MQ In-process Transport \- transport to pass messages between threads
-.SH SYNOPSIS
-
-In-process transport is optimised for passing messages between 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_ipc (7)
-.BR zmq_tcp (7)
-.BR zmq_udp (7)
-.BR zmq_pgm (7)
-
-.SH AUTHOR
-Martin Sustrik <sustrik at 250bpm dot com>
-