- 23 Nov, 2017 1 commit
-
-
fnaime authored
Problem: Wrong linger default value Solution: correct documentation
-
- 16 Nov, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add them
-
- 10 Nov, 2017 1 commit
-
-
ebyrob authored
-
- 25 Oct, 2017 1 commit
-
-
f18m authored
Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
-
- 21 Oct, 2017 1 commit
-
-
Simon Giesecke authored
Solution: provide correct description Fixes #2789
-
- 18 Oct, 2017 1 commit
-
-
Simon Giesecke authored
* Clarify usage of zmq_close
-
- 17 Oct, 2017 5 commits
-
-
Luca Boccassi authored
Solution: mention that the STATISTICS command returns a message with 8 frames
-
Luca Boccassi authored
Solution: fix it
-
f18m authored
-
f18m authored
-
f18m authored
-
- 16 Oct, 2017 2 commits
-
-
Luca Boccassi authored
Solution: add a section in zmq_ctx_set's manpage
-
Luca Boccassi authored
Solution: mention that it is used on Linux when SCHED_OTHER is selected
-
- 09 Oct, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add ZMQ_ZAP_ENFORCE_DOMAIN to hide backward incompatible change and make it disabled by default. In a future release that breaks API compatibility we can then switch the default to enabled in order to achieve full RFC compatibility. Fixes #2762
-
- 19 Sep, 2017 4 commits
- 07 Sep, 2017 4 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: use "routing_id" instead
-
sigiesec authored
Solution: Replaced by "routing id"
-
sigiesec authored
Solution: change docs to refer to "Routing id"
-
- 20 Aug, 2017 1 commit
-
-
Simon Giesecke authored
Solution: relaxed assertion to accept 10% of the SNDHWM, and updated documentation accordingly
-
- 19 Aug, 2017 1 commit
-
-
Luca Boccassi authored
Solution: as discussed, remove the deprecation notices, as many users expressed the need for multi-part support. Fixes #2699
-
- 18 Aug, 2017 1 commit
-
-
sigiesec authored
state of ZMQ_EVENT_HANDSHAKE_FAILED_* events Solution: update documentation
-
- 17 Aug, 2017 1 commit
-
-
Min RK authored
group being a `char *` is logically a text type, which needs an encoding. Declare in the API that groups shall be UTF8-encoded, matching the `zmq_msg_gets` API, which is the other user-facing `char *` API, which has the same definition. This allows bindings to provide text-type APIs, which they cannot do if arbitrary bytes are allowed
-
- 04 Aug, 2017 2 commits
-
-
Simon Giesecke authored
Solution: add documentation
-
Simon Giesecke authored
Solution: Remove from documentation
-
- 31 Jul, 2017 1 commit
-
-
Brian Russell authored
Linux now supports Virtual Routing and Forwarding (VRF) as per: https://www.kernel.org/doc/Documentation/networking/vrf.txt In order for an application to bind or connect to a socket with an address in a VRF, they need to first bind the socket to the VRF device: setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1); Note "dev" is the VRF device, eg. VRF "blue", rather than an interface enslaved to the VRF. Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device. In general, if a socket is bound to a device, eg. an interface, only packets received from that particular device are processed by the socket. If device is a VRF device, then subsequent binds/connects to that socket use addresses in the VRF routing table.
-
- 14 Jul, 2017 1 commit
-
-
Marc Sune authored
Solution: * Document the new behaviour when generating 'ZMQ_POLLOUT' events for ZMQ_ROUTER sockets with 'ZMQ_ROUTER_MANDATORY' set to `1` * Add clarifications for 'ZMQ_ROUTER' socket when 'ZMQ_ROUTER_MANDATORY' is set to `1`
-
- 23 Jun, 2017 1 commit
-
-
Emanuel Koczwara authored
Fixed minor typo.
-
- 24 Apr, 2017 1 commit
-
-
Jim Garlick authored
Problem: GSSAPI NAMETYPE options were not documented in man pages for zmq_getsockopt() and zmq_setsockopt(). Solution: add new options to these manual pages.
-
- 21 Apr, 2017 2 commits
-
-
Jim Garlick authored
Problem: zmq_gssapi.7 was not mentioned in doc/Makefile.am Solution: add man page to MAN7 in doc/Makefile.am
-
Jim Garlick authored
Problem: new GSSAPI socket options are not documented. Solution: add PRINCIPAL NAMES section to zmq_gssapi.7
-
- 20 Apr, 2017 1 commit
-
-
Jim Garlick authored
Problem: the ZMQ_GSSAPI_PRINCIPAL socket option is described as mandatory in the zmq_gssapi(7) manual page. In fact it is optional. Solution: Describe ZMQ_GSSAPI_PRINCIPAL as optional. If unspecified, default credentials are used.
-
- 23 Feb, 2017 1 commit
-
-
Takeshi Abe authored
Solution: fix it
-
- 19 Jan, 2017 2 commits
-
-
Luca Boccassi authored
Solution: fix it
-
Asmod4n authored
-
- 03 Jan, 2017 2 commits
-
-
Luca Boccassi authored
Solution: mention this in the documentation
-
Patrik Wenger authored
-