diff options
| author | Martin Sustrik <sustrik@250bpm.com> | 2011-03-23 17:01:39 +0100 |
|---|---|---|
| committer | Martin Sustrik <sustrik@250bpm.com> | 2011-03-23 17:01:39 +0100 |
| commit | b45b68ae4ab90af1ce35deec52b0c0492a1f49d4 (patch) | |
| tree | b5ad48702e03088b957fab8ea31e90029270ec41 /doc/zmq_setsockopt.txt | |
| parent | f5e6d67948b8c71c2444046f6246aebab16546dc (diff) | |
ZMQ_MCAST_LOOP removed
Multicast loopback is not a real multicast, rather a kernel-space
simulation. Moreover, it tends to be rather unreliable and lossy.
Removing the option will force users to use transports better
suited for the job, such as inproc or ipc.
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
Diffstat (limited to 'doc/zmq_setsockopt.txt')
| -rw-r--r-- | doc/zmq_setsockopt.txt | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/doc/zmq_setsockopt.txt b/doc/zmq_setsockopt.txt index 6c7046e..9387116 100644 --- a/doc/zmq_setsockopt.txt +++ b/doc/zmq_setsockopt.txt @@ -197,23 +197,6 @@ Default value:: -1 Applicable socket types:: all, when using multicast transports -ZMQ_MCAST_LOOP: Control multicast loop-back -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The 'ZMQ_MCAST_LOOP' option shall control whether data sent via multicast -transports using the specified 'socket' can also be received by the sending -host via loop-back. A value of zero disables the loop-back functionality, while -the default value of 1 enables the loop-back functionality. Leaving multicast -loop-back enabled when it is not required can have a negative impact on -performance. Where possible, disable 'ZMQ_MCAST_LOOP' in production -environments. - -[horizontal] -Option value type:: int64_t -Option value unit:: boolean -Default value:: 1 -Applicable socket types:: all, when using multicast transports - - ZMQ_SNDBUF: Set kernel transmit buffer size ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The 'ZMQ_SNDBUF' option shall set the underlying kernel transmit buffer size |