mirror of
https://github.com/saltstack/salt.git
synced 2025-04-17 10:10:20 +00:00
Fix ZeroMQ references
This commit is contained in:
parent
398ace3df1
commit
b85abf1bce
1 changed files with 7 additions and 7 deletions
|
@ -1,26 +1,26 @@
|
|||
================
|
||||
Zeromq Transport
|
||||
ZeroMQ Transport
|
||||
================
|
||||
|
||||
.. note::
|
||||
|
||||
Zeromq is the current default transport within Salt
|
||||
ZeroMQ is the current default transport within Salt
|
||||
|
||||
Zeromq is a messaging library with bindings into many languages. Zeromq implements
|
||||
ZeroMQ is a messaging library with bindings into many languages. ZeroMQ implements
|
||||
a socket interface for message passing, with specific semantics for the socket type.
|
||||
|
||||
|
||||
Publish Server and Client
|
||||
=========================
|
||||
The publish server and client are implemented using zeromq's pub/sub sockets. By
|
||||
default we don't use zeromq's filtering, which means that all publish jobs are
|
||||
sent to all minions and filtered minion side. Zeromq does have publisher side
|
||||
The publish server and client are implemented using ZeroMQ's pub/sub sockets. By
|
||||
default we don't use ZeroMQ's filtering, which means that all publish jobs are
|
||||
sent to all minions and filtered minion side. ZeroMQ does have publisher side
|
||||
filtering which can be enabled in salt using :conf_master:`zmq_filtering`.
|
||||
|
||||
|
||||
Request Server and Client
|
||||
=========================
|
||||
The request server and client are implemented using zeromq's req/rep sockets.
|
||||
The request server and client are implemented using ZeroMQ's req/rep sockets.
|
||||
These sockets enforce a send/recv pattern, which forces salt to serialize
|
||||
messages through these socket pairs. This means that although the interface is
|
||||
asynchronous on the minion we cannot send a second message until we have
|
||||
|
|
Loading…
Add table
Reference in a new issue