diff options
author | Martin Lucina <mato@kotelna.sk> | 2010-02-10 16:18:46 +0100 |
---|---|---|
committer | Martin Lucina <mato@kotelna.sk> | 2010-02-10 16:18:46 +0100 |
commit | 354efc513fdb4096f8830e6c2e3e8f1311303e61 (patch) | |
tree | c8dec6949c70e6f41832e42326594ebb889b1ee2 /doc/zmq_inproc.txt | |
parent | 2d44bf3644c8e12aa86c48e9da4df19bfa9ea703 (diff) |
Convert documentation to AsciiDoc
Diffstat (limited to 'doc/zmq_inproc.txt')
-rw-r--r-- | doc/zmq_inproc.txt | 50 |
1 files changed, 50 insertions, 0 deletions
diff --git a/doc/zmq_inproc.txt b/doc/zmq_inproc.txt new file mode 100644 index 0000000..7861201 --- /dev/null +++ b/doc/zmq_inproc.txt @@ -0,0 +1,50 @@ +zmq_inproc(7) +============= + + +NAME +---- +zmq_inproc - 0MQ transport to pass messages between threads + + +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 (linkzmq:zmq_init[3]) with zero I/O worker threads. + + +CONNECTION STRING +----------------- +Connection string for inproc transport is "inproc://" followed by an arbitrary +string. There are no restrictions on the string format: + +---- + inproc://my_endpoint + inproc://feeds/opra/cboe + inproc://feeds.opra.nasdaq + inproc://!&W#($)_@_123*((^^^ +---- + + +WIRE FORMAT +----------- +In-process transport transfers messages via memory thus there is no need for a +wire format specification. + + +SEE ALSO +-------- +linkzmq:zmq_ipc[7] +linkzmq:zmq_tcp[7] +linkzmq:zmq_udp[7] +linkzmq:zmq_pgm[7] + + +AUTHOR +------ +Martin Sustrik <sustrik at 250bpm dot com> |