Skip to content

Commit 64db7d2

Browse files
githejiebluca
authored andcommitted
Fix format issue of zmq_socket.adoc
1 parent 1f4dd54 commit 64db7d2

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

doc/zmq_socket.adoc

+7-7
Original file line numberDiff line numberDiff line change
@@ -164,7 +164,7 @@ Groups are matched using exact matching (vs prefix matching of PubSub).
164164
NOTE: Radio-dish is still in draft phase.
165165

166166
ZMQ_RADIO
167-
^^^^^^^
167+
^^^^^^^^^
168168
A socket of type 'ZMQ_RADIO' is used by a _publisher_ to distribute data.
169169
Each message belong to a group, a group is specified with xref:zmq_msg_set_group.adoc[zmq_msg_set_group]
170170
Messages are distributed to all members of a group.
@@ -339,15 +339,15 @@ Outgoing routing strategy:: N/A
339339
Action in mute state:: Block
340340

341341
Scatter-gather pattern
342-
~~~~~~~~~~~~~~~~
342+
~~~~~~~~~~~~~~~~~~~~~~
343343
The scatter-gather pattern is the thread-safe version of the pipeline pattern.
344344
The scatter-gather pattern is used for distributing data to _nodes_ arranged in
345345
a pipeline. Data always flows down the pipeline, and each stage of the pipeline
346346
is connected to at least one _node_. When a pipeline stage is connected to
347347
multiple _nodes_ data is round-robined among all connected _nodes_.
348348

349349
ZMQ_SCATTER
350-
^^^^^^^^
350+
^^^^^^^^^^^
351351
A socket of type 'ZMQ_SCATTER' is used by a scatter-gather _node_ to send messages
352352
to downstream scatter-gather _nodes_. Messages are round-robined to all connected
353353
downstream _nodes_. The _zmq_recv()_ function is not implemented for this
@@ -374,7 +374,7 @@ Action in mute state:: Block
374374

375375

376376
ZMQ_GATHER
377-
^^^^^^^^
377+
^^^^^^^^^^
378378
A socket of type 'ZMQ_GATHER' is used by a scatter-gather _node_ to receive messages
379379
from upstream scatter-gather _nodes_. Messages are fair-queued from among all
380380
connected upstream _nodes_. The _zmq_send()_ function is not implemented for
@@ -433,7 +433,7 @@ Action in mute state:: Block
433433

434434

435435
Peer-to-peer pattern
436-
~~~~~~~~~~~~~~~~~~~~~~
436+
~~~~~~~~~~~~~~~~~~~~
437437

438438
The peer-to-peer pattern is used to connect a peer to multiple peers.
439439
Peer can both connect and bind and mix both of them with the same socket.
@@ -474,7 +474,7 @@ Incoming routing strategy:: Fair-queued
474474
Action in mute state:: Return EAGAIN
475475

476476
Channel pattern
477-
~~~~~~~~~~~~~~~~~~~~~~
477+
~~~~~~~~~~~~~~~
478478
The channel pattern is the thread-safe version of the exclusive pair pattern.
479479
The channel pattern is used to connect a peer to precisely one other
480480
peer. This pattern is used for inter-thread communication across the inproc
@@ -483,7 +483,7 @@ transport.
483483
NOTE: Channel is still in draft phase.
484484

485485
ZMQ_CHANNEL
486-
^^^^^^^^
486+
^^^^^^^^^^^
487487
A socket of type 'ZMQ_CHANNEL' can only be connected to a single peer at any one
488488
time. No message routing or filtering is performed on messages sent over a
489489
'ZMQ_CHANNEL' socket.

0 commit comments

Comments
 (0)