@@ -164,7 +164,7 @@ Groups are matched using exact matching (vs prefix matching of PubSub).
164
164
NOTE: Radio-dish is still in draft phase.
165
165
166
166
ZMQ_RADIO
167
- ^^^^^^^
167
+ ^^^^^^^^^
168
168
A socket of type 'ZMQ_RADIO' is used by a _publisher_ to distribute data.
169
169
Each message belong to a group, a group is specified with xref:zmq_msg_set_group.adoc[zmq_msg_set_group]
170
170
Messages are distributed to all members of a group.
@@ -339,15 +339,15 @@ Outgoing routing strategy:: N/A
339
339
Action in mute state:: Block
340
340
341
341
Scatter-gather pattern
342
- ~~~~~~~~~~~~~~~~
342
+ ~~~~~~~~~~~~~~~~~~~~~~
343
343
The scatter-gather pattern is the thread-safe version of the pipeline pattern.
344
344
The scatter-gather pattern is used for distributing data to _nodes_ arranged in
345
345
a pipeline. Data always flows down the pipeline, and each stage of the pipeline
346
346
is connected to at least one _node_. When a pipeline stage is connected to
347
347
multiple _nodes_ data is round-robined among all connected _nodes_.
348
348
349
349
ZMQ_SCATTER
350
- ^^^^^^^^
350
+ ^^^^^^^^^^^
351
351
A socket of type 'ZMQ_SCATTER' is used by a scatter-gather _node_ to send messages
352
352
to downstream scatter-gather _nodes_. Messages are round-robined to all connected
353
353
downstream _nodes_. The _zmq_recv()_ function is not implemented for this
@@ -374,7 +374,7 @@ Action in mute state:: Block
374
374
375
375
376
376
ZMQ_GATHER
377
- ^^^^^^^^
377
+ ^^^^^^^^^^
378
378
A socket of type 'ZMQ_GATHER' is used by a scatter-gather _node_ to receive messages
379
379
from upstream scatter-gather _nodes_. Messages are fair-queued from among all
380
380
connected upstream _nodes_. The _zmq_send()_ function is not implemented for
@@ -433,7 +433,7 @@ Action in mute state:: Block
433
433
434
434
435
435
Peer-to-peer pattern
436
- ~~~~~~~~~~~~~~~~~~~~~~
436
+ ~~~~~~~~~~~~~~~~~~~~
437
437
438
438
The peer-to-peer pattern is used to connect a peer to multiple peers.
439
439
Peer can both connect and bind and mix both of them with the same socket.
@@ -474,7 +474,7 @@ Incoming routing strategy:: Fair-queued
474
474
Action in mute state:: Return EAGAIN
475
475
476
476
Channel pattern
477
- ~~~~~~~~~~~~~~~~~~~~~~
477
+ ~~~~~~~~~~~~~~~
478
478
The channel pattern is the thread-safe version of the exclusive pair pattern.
479
479
The channel pattern is used to connect a peer to precisely one other
480
480
peer. This pattern is used for inter-thread communication across the inproc
@@ -483,7 +483,7 @@ transport.
483
483
NOTE: Channel is still in draft phase.
484
484
485
485
ZMQ_CHANNEL
486
- ^^^^^^^^
486
+ ^^^^^^^^^^^
487
487
A socket of type 'ZMQ_CHANNEL' can only be connected to a single peer at any one
488
488
time. No message routing or filtering is performed on messages sent over a
489
489
'ZMQ_CHANNEL' socket.
0 commit comments