- 27 Jun, 2019 2 commits
-
-
Luca Boccassi authored
Solution: clearly advise users to avoid them in all cases to avoid unforseen problems. Also fix markdown syntax, applicable transport types and getter description.
-
jean-airoldie authored
Solution: Added a socket option to configure them at runtime.
-
- 10 Jun, 2019 1 commit
-
-
Christophe Guillon authored
-
- 18 May, 2019 1 commit
-
-
Luca Boccassi authored
Solution: fix them
-
- 17 May, 2019 1 commit
-
-
imkcy9 authored
Support XPub socket send last value caching to last subscription pipe with ZMQ_XPUB_MANUAL_LAST_VALUE. (#3511) * Add ZMQ_XPUB_MANUAL_LAST_VALUE * Surpport xpub send last value caching to one pipe with ZMQ_XPUB_MANUAL_LAST_VALUE * Add test_xpubub_manual_last_value * Add relicense and doc
-
- 12 Apr, 2019 1 commit
-
-
Luca Boccassi authored
Solution: add space between OR'ed values zmq_getsockopt.3 2472: warning [p 17, 9.5i, div '3tbd1,1', 0.5i]: can't break line zmq_setsockopt.3 3471: warning [p 24, 1.8i, div '3tbd1,1', 0.5i]: can't break line
-
- 14 Dec, 2018 1 commit
-
-
Erick Tryzelaar authored
Noticed there was a small typo in the documentation.
-
- 13 Sep, 2018 1 commit
-
-
Francesco Montorsi authored
Add new HWM tests and more detailed documentation
-
- 15 Aug, 2018 1 commit
-
-
Szekely Gyorgy authored
* Add ZMQ_ROUTER_NOTIFY draft socket option
-
- 26 Jun, 2018 1 commit
-
-
jamesdillonharvey authored
* More info on conflate queue
-
- 25 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: use UINT16_MAX
-
- 14 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: add initial documentation
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 28 Apr, 2018 1 commit
-
-
Luca Boccassi authored
Solution: mention in manpage that if the timeout is not set and the interval is, the timeout will be equal to the interval
-
- 23 Mar, 2018 2 commits
-
-
Luca Boccassi authored
Solution: revert the revert! Revert "Problem: regression in 4.2.3 went unnoticed, want to release 4.2.5" This reverts commit 5f17e26f.
-
Luca Boccassi authored
Solution: revert DRAFT -> STABLE API transition so that we can do a bugfix-only 4.2.5 release. Will be re-reverted once tagged. Revert "Problem: ZMQ_BINDTODEVICE has met STABLE conditions" This reverts commit 3cb79f50. Revert "Problem: ZMQ_MSG_GSSAPI_* have met STABLE conditions" This reverts commit 374da420. Revert "Problem: ZMQ_MSG_T_SIZE has met STABLE conditions" This reverts commit 6411c4a2. Revert "Problem: docs say STABLE API still in DRAFT" This reverts commit 9f2f30b7.
-
- 21 Mar, 2018 1 commit
-
-
Luca Boccassi authored
Solution: update them
-
- 15 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
-
- 02 Mar, 2018 1 commit
-
-
Luca Boccassi authored
Solultion: clarify that notifications for unique subs/unsubs are always passed, and these option only affect the behaviour for duplicated ones.
-
- 23 Nov, 2017 1 commit
-
-
fnaime authored
Problem: Wrong linger default value Solution: correct documentation
-
- 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 3 commits
- 07 Sep, 2017 3 commits
-
-
Doron Somech authored
-
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
-
- 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`
-
- 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.
-
- 03 Jan, 2017 1 commit
-
-
Patrik Wenger authored
-
- 26 Dec, 2016 2 commits
-
-
Luca Boccassi authored
Solution: add paragraphs to zmq_get/setsockopt man pages
-
Luca Boccassi authored
Solution: add manpage
-
- 16 Nov, 2016 1 commit
-
-
Andreas Rottmann authored
This addresses #2169.
-
- 03 Jun, 2016 1 commit
-
-
Ricardo Catalinas Jiménez authored
-
- 01 May, 2016 1 commit
-
-
hitstergtd authored
Solution: - Update formatting and remove redundant parts from ZMQ_PROBE_ROUTER, ZMQ_USE_FD, ZMQ_TCP_MAXRT, ZMQ_TCP_TOS - Only cosmetic changes to the content - These changes already merged on api.zeromq.org by me
-
- 20 Mar, 2016 1 commit
-
-
Frederic Tregon authored
Problem: when using ZMQ_REQ_RELAXED + ZMQ_REQ_CORRELATE and two 'send' are executed in a row and no server is available at the time of the sends, then the internal request_id used to identify messages gets corrupted and the two messages end up with the same request_id. The correlation no longer works in that case and you may end up with the wrong message. Solution: make a copy of the request_id instance member before sending it down the pipe.
-
- 09 Feb, 2016 2 commits
-
-
Pieter Hintjens authored
These options are confusing and redundant. Their names suggest they apply to the tcp:// transport, yet they are used for all stream protocols. The methods zmq::set_tcp_receive_buffer and zmq::set_tcp_send_buffer don't use these values at all, they use ZMQ_SNDBUF and ZMQ_RCVBUF. Solution: merge these new options into ZMQ_SNDBUF and ZMQ_RCVBUF. This means defaulting these two options to 8192, and removing the new options. We now have ZMQ_SNDBUF and ZMQ_RCVBUF being used both for TCP socket control, and for input/output buffering. Note: the default for SNDBUF and RCVBUF are otherwise 4096.
-
Pieter Hintjens authored
This option has a few issues. The name is long and clumsy. The functonality is not smooth: one must set both this and ZMQ_XPUB_VERBOSE at the same time, or things will break mysteriously. Solution: rename to ZMQ_XPUB_VERBOSER and make an atomic option. That is, implicitly does ZMQ_XPUB_VERBOSE.
-