blob: 0c84641e4cc98ddbecd5a609e503ad92b5e03385 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
|
.TH zmq_inproc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
.SH NAME
In-process (inter-thread) tranport for 0MQ
.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>
|
