From 296beecd24818cf0e86c72eeb2eda1cd224457dd Mon Sep 17 00:00:00 2001 From: JaeSang Yoo Date: Sat, 7 Mar 2020 14:34:20 +0900 Subject: [PATCH 1/2] Problem: UDP is not mentioned in bind and connect zmq_bind(3) and zmq_connect(3) does not mention UDP as available transport types. Solution: add udp mentioning line for related docs --- doc/zmq_bind.txt | 1 + doc/zmq_connect.txt | 1 + 2 files changed, 2 insertions(+) diff --git a/doc/zmq_bind.txt b/doc/zmq_bind.txt index 7ce96edb..79ec10aa 100644 --- a/doc/zmq_bind.txt +++ b/doc/zmq_bind.txt @@ -28,6 +28,7 @@ The 'endpoint' is a string consisting of a 'transport'`://` followed by an 'inproc':: local in-process (inter-thread) communication transport, see linkzmq:zmq_inproc[7] 'pgm', 'epgm':: reliable multicast transport using PGM, see linkzmq:zmq_pgm[7] 'vmci':: virtual machine communications interface (VMCI), see linkzmq:zmq_vmci[7] +'udp':: unreliable unicast and multicast using UDP, see linkzmq:zmq_udp[7] Every 0MQ socket type except 'ZMQ_PAIR' supports one-to-many and many-to-one semantics. The precise semantics depend on the socket type and are defined in diff --git a/doc/zmq_connect.txt b/doc/zmq_connect.txt index f23e7af6..bf21736d 100644 --- a/doc/zmq_connect.txt +++ b/doc/zmq_connect.txt @@ -28,6 +28,7 @@ The 'endpoint' is a string consisting of a 'transport'`://` followed by an 'inproc':: local in-process (inter-thread) communication transport, see linkzmq:zmq_inproc[7] 'pgm', 'epgm':: reliable multicast transport using PGM, see linkzmq:zmq_pgm[7] 'vmci':: virtual machine communications interface (VMCI), see linkzmq:zmq_vmci[7] +'udp':: unreliable unicast and multicast using UDP, see linkzmq:zmq_udp[7] Every 0MQ socket type except 'ZMQ_PAIR' supports one-to-many and many-to-one semantics. The precise semantics depend on the socket type and are defined in From ded0d83e4737607176f1de97d993edea165d2bcc Mon Sep 17 00:00:00 2001 From: JaeSang Yoo Date: Sat, 7 Mar 2020 14:55:01 +0900 Subject: [PATCH 2/2] Problem: wildcard address with udp not mentioned * UDP is mentioned as available transport, and it also supports wildcard addresses, but not mentioned * zmq_unbind(7) also mentions about wild-card endpoint in zmq_bind(3) Solution: add udp in wildcard address related docs --- doc/zmq_bind.txt | 5 +++-- doc/zmq_unbind.txt | 6 +++--- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/zmq_bind.txt b/doc/zmq_bind.txt index 79ec10aa..6e3f4cc1 100644 --- a/doc/zmq_bind.txt +++ b/doc/zmq_bind.txt @@ -34,8 +34,9 @@ Every 0MQ socket type except 'ZMQ_PAIR' supports one-to-many and many-to-one semantics. The precise semantics depend on the socket type and are defined in linkzmq:zmq_socket[3]. -The 'ipc', 'tcp' and 'vmci' transports accept wildcard addresses: see linkzmq:zmq_ipc[7], -linkzmq:zmq_tcp[7] and linkzmq:zmq_vmci[7] for details. +The 'ipc', 'tcp', 'vmci' and 'udp' transports accept wildcard addresses: see +linkzmq:zmq_ipc[7], linkzmq:zmq_tcp[7], linkzmq:zmq_vmci[7] and +linkzmq:zmq_udp[7] for details. NOTE: the address syntax may be different for _zmq_bind()_ and _zmq_connect()_ especially for the 'tcp', 'pgm' and 'epgm' transports. diff --git a/doc/zmq_unbind.txt b/doc/zmq_unbind.txt index 92e9b7ed..1ae33b18 100644 --- a/doc/zmq_unbind.txt +++ b/doc/zmq_unbind.txt @@ -28,9 +28,9 @@ The 'endpoint' argument is as described in linkzmq:zmq_bind[3] Unbinding wild-card address from a socket ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When wild-card `*` 'endpoint' (described in linkzmq:zmq_tcp[7], -linkzmq:zmq_ipc[7] and linkzmq:zmq_vmci[7]) was used in _zmq_bind()_, the caller should use -real 'endpoint' obtained from the ZMQ_LAST_ENDPOINT socket option -to unbind this 'endpoint' from a socket. +linkzmq:zmq_ipc[7], linkzmq:zmq_udp[7] and linkzmq:zmq_vmci[7]) was used in +_zmq_bind()_, the caller should use real 'endpoint' obtained from the +ZMQ_LAST_ENDPOINT socket option to unbind this 'endpoint' from a socket. RETURN VALUE ------------