- 13 Sep, 2019 1 commit
-
-
Tobias Schlüter authored
Solution: don't include winsock2.h, replace its only use (reference to SOCKET) by explicitly naming underlying type.
-
- 27 Aug, 2019 1 commit
-
-
Francesco Montorsi authored
* Introduce DRAFT zmq_ctx_set_ext() and zmq_ctx_get_ext() methods. Change ZMQ_THREAD_NAME_PREFIX to allow for non-numeric thread name prefixes.
-
- 27 Jul, 2019 1 commit
-
-
Brian Carcich authored
how it declares the file descriptor (fd) of a socket in struct zmq_pollitem_t vs. struct zmq_poller_event_t Solution: Make include/zmq.h consistent in this matter
-
- 16 Jul, 2019 1 commit
-
-
somdoron authored
Solution: implement ZWS 2.0 which websocket transport for zeromq
-
- 08 Jul, 2019 1 commit
-
-
Luca Boccassi authored
Solution: bump to 4.3.3
-
- 27 Jun, 2019 1 commit
-
-
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: unify the two APIs, as they are both still in DRAFT state and thus can be changed.
-
- 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
-
- 15 May, 2019 1 commit
-
-
jean-airoldie authored
Solution: Allow ZMQ_PUB and ZMQ_PUSH sockets types for the monitoring. This way someone could create a ZMQ_PULL socket connected to multiple monitoring sockets at the same time.
-
- 09 May, 2019 2 commits
-
-
Simon Giesecke authored
Solution: change return type to int (again) and return fd via an output parameter
-
Simon Giesecke authored
Solution: use proper fd_t type, and also define and use a zmq_fd_t in the API
-
- 28 Apr, 2019 1 commit
-
-
jean-airoldie authored
Solution: Add a method to get the zmq_poller's signaler fd. Then we can associate a poller instance with every thread safe socket and use its fd.
-
- 10 Feb, 2019 1 commit
-
-
Luca Boccassi authored
Solution: add API and ZMQ_EVENT_PIPES_STATS event which generates 2 values, one for the egress and one for the ingress pipes respectively. Refactor the events code to be able to send multiple values.
-
- 03 Feb, 2019 1 commit
-
-
Luca Boccassi authored
Solution: define uint64_t if not available in the system headers and remove inclusion of inttypes.h which does not exist and is already conditionally included in zmq.h if required, do not use PRIx64
-
- 02 Feb, 2019 2 commits
-
-
Simon Giesecke authored
Solution: add definition to zmq.h
-
Simon Giesecke authored
Solution: add monitor event socket option
-
- 12 Jan, 2019 1 commit
-
-
Luca Boccassi authored
Solution: bump ABI and revisions and changelog now that v4.3.1 is out
-
- 28 Nov, 2018 1 commit
-
-
Luca Boccassi authored
Solution: bump to 5.2.1 and 4.3.1 respectively
-
- 18 Nov, 2018 3 commits
-
-
Luca Boccassi authored
Solution: do it
-
Luca Boccassi authored
Solution: do it
-
Luca Boccassi authored
Solution: do it
-
- 01 Nov, 2018 1 commit
-
-
Luca Boccassi authored
Solution: bump back from 4.3.1 to 4.3.0
-
- 15 Aug, 2018 1 commit
-
-
Szekely Gyorgy authored
* Add ZMQ_ROUTER_NOTIFY draft socket option
-
- 27 Jul, 2018 1 commit
-
-
Luca Boccassi authored
Solution: move them from DRAFT state to STABLE
-
- 26 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 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 4 commits
-
-
Luca Boccassi authored
Solution: move them from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed.
-
Luca Boccassi authored
Solution: move them from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed.
-
Luca Boccassi authored
Solution: move it from DRAFT to STABLE since it's been in a public release, committed for 6+ months and has not changed. Given a new STABLE symbol has been added, bump minor version number.
-
Luca Boccassi authored
Solution: bump to 4.2.5
-
- 14 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
Lets the application set per-connection metadata. Metadata is specified as "X-key:value" and set using zmq_setsockopt, eg: zmq_setsockopt (s, ZMQ_METADATA, "X-key:value", 11); The peer can then obtain the metadata from a received message: char *data = zmq_msg_gets(msg, "X-key");
-
- 05 Mar, 2018 1 commit
-
-
Stefan Kaes authored
The zero copy decoding strategy implemented for 4.2.0 can lead to a large increase of main memory usage in some cases (I have seen one program go up to 40G from 10G after upgrading from 4.1.4). This commit adds a new option to contexts, called ZMQ_ZERO_COPY_RECV, which allows one to switch to the old decoding strategy.
-
- 09 Feb, 2018 2 commits
-
-
Simon Giesecke authored
Solution: add socket option
-
sigiesec authored
Solution: relaxed test assertions, based on the actual time passed, instead of assuming that this equals to the time slept
-
- 08 Feb, 2018 1 commit
-
-
Tetsuya Hayashi authored
-
- 04 Feb, 2018 1 commit
-
-
Luca Boccassi authored
-
- 03 Feb, 2018 1 commit
-
-
Tetsuya Hayashi authored
-