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_pgm.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_pgm.txt')
| -rw-r--r-- | doc/zmq_pgm.txt | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/zmq_pgm.txt b/doc/zmq_pgm.txt index d9bce5a..91b1678 100644 --- a/doc/zmq_pgm.txt +++ b/doc/zmq_pgm.txt @@ -23,9 +23,8 @@ UDP datagrams (the 'epgm' transport). The 'pgm' and 'epgm' transports can only be used with the 'ZMQ_PUB' and 'ZMQ_SUB' socket types. -Further, PGM sockets are rate limited by default and incur a performance -penalty when used over a loop-back interface. For details, refer to the -'ZMQ_RATE', 'ZMQ_RECOVERY_IVL' and 'ZMQ_MCAST_LOOP' options documented in +Further, PGM sockets are rate limited by default. For details, refer to the +'ZMQ_RATE', and 'ZMQ_RECOVERY_IVL' options documented in linkzmq:zmq_setsockopt[3]. CAUTION: The 'pgm' transport implementation requires access to raw IP sockets. |