Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
ee3444ff
Commit
ee3444ff
authored
Sep 04, 2010
by
Martin Lucina
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: Update zmq_socket(3) for 2.0.8 API changes
parent
26b39bcd
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
22 additions
and
18 deletions
+22
-18
zmq_socket.txt
doc/zmq_socket.txt
+22
-18
No files found.
doc/zmq_socket.txt
View file @
ee3444ff
...
...
@@ -216,22 +216,24 @@ is connected to at least one _node_. When a pipeline stage is connected to
multiple _nodes_ data is load-balanced among all connected _nodes_.
ZMQ_
DOWNSTREAM
^^^^^^^^
^^^^^^
A socket of type 'ZMQ_
DOWNSTREAM
' is used by a pipeline _node_ to send messages
ZMQ_
PUSH
^^^^^^^^
A socket of type 'ZMQ_
PUSH
' is used by a pipeline _node_ to send messages
to downstream pipeline _nodes_. Messages are load-balanced to all connected
downstream _nodes_. The _zmq_recv()_ function is not implemented for this
socket type.
When a 'ZMQ_DOWNSTREAM' socket enters an exceptional state due to having
reached the high water mark for all downstream _nodes_, or if there are no
downstream _nodes_ at all, then any linkzmq:zmq_send[3] operations on the
socket shall block until the exceptional state ends or at least one downstream
_node_ becomes available for sending; messages are not discarded.
When a 'ZMQ_PUSH' socket enters an exceptional state due to having reached the
high water mark for all downstream _nodes_, or if there are no downstream
_nodes_ at all, then any linkzmq:zmq_send[3] operations on the socket shall
block until the exceptional state ends or at least one downstream _node_
becomes available for sending; messages are not discarded.
Deprecated alias: 'ZMQ_DOWNSTREAM'.
[horizontal]
.Summary of ZMQ_
DOWNSTREAM
characteristics
Compatible peer sockets:: 'ZMQ_
UPSTREAM
'
.Summary of ZMQ_
PUSH
characteristics
Compatible peer sockets:: 'ZMQ_
PULL
'
Direction:: Unidirectional
Send/receive pattern:: Send only
Incoming routing strategy:: N/A
...
...
@@ -239,16 +241,18 @@ Outgoing routing strategy:: Load-balanced
ZMQ_HWM option action:: Block
ZMQ_UPSTREAM
^^^^^^^^^^^^
A socket of type 'ZMQ_UPSTREAM' is used by a pipeline _node_ to receive
messages from upstream pipeline _nodes_. Messages are fair-queued from among
all connected upstream _nodes_. The _zmq_send()_ function is not implemented
for this socket type.
ZMQ_PULL
^^^^^^^^
A socket of type 'ZMQ_PULL' is used by a pipeline _node_ to receive messages
from upstream pipeline _nodes_. Messages are fair-queued from among all
connected upstream _nodes_. The _zmq_send()_ function is not implemented for
this socket type.
Deprecated alias: 'ZMQ_UPSTREAM'.
[horizontal]
.Summary of ZMQ_
UPSTREAM
characteristics
Compatible peer sockets:: 'ZMQ_
DOWNSTREAM
'
.Summary of ZMQ_
PULL
characteristics
Compatible peer sockets:: 'ZMQ_
PUSH
'
Direction:: Unidirectional
Send/receive pattern:: Receive only
Incoming routing strategy:: Fair-queued
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment