2010-01-05 08:29:35 +01:00
|
|
|
.TH zmq_inproc 7 "" "(c)2007-2010 iMatix Corporation" "0MQ User Manuals"
|
2009-12-03 12:58:16 +01:00
|
|
|
.SH NAME
|
2010-01-18 13:16:14 +01:00
|
|
|
In-process (inter-thread) transport for 0MQ
|
2009-12-03 12:58:16 +01:00
|
|
|
.SH SYNOPSIS
|
2010-01-13 15:15:01 +01:00
|
|
|
|
2010-01-15 14:11:39 +01:00
|
|
|
In-process transport is optimised for passing messages between threads in the
|
2010-01-13 15:15:01 +01:00
|
|
|
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.
|
|
|
|
|
|
2009-12-03 12:58:16 +01:00
|
|
|
.SH "SEE ALSO"
|
2010-01-13 15:15:01 +01:00
|
|
|
|
2010-01-15 14:11:39 +01:00
|
|
|
.BR zmq_ipc (7)
|
2010-01-13 15:15:01 +01:00
|
|
|
.BR zmq_tcp (7)
|
|
|
|
|
.BR zmq_udp (7)
|
|
|
|
|
.BR zmq_pgm (7)
|
|
|
|
|
|
2009-12-03 12:58:16 +01:00
|
|
|
.SH AUTHOR
|
2009-12-04 10:06:46 +01:00
|
|
|
Martin Sustrik <sustrik at 250bpm dot com>
|
2009-12-03 12:58:16 +01:00
|
|
|
|
