- 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 4 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.
-
Pieter Hintjens authored
Solution: rename to ZMQ_MAXRT This is the option name used on Windows, so easier to use and remember.
-
Luca Boccassi authored
Solution: rename socket option (and variables and files) from usefd to use_fd.
-
- 08 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: rename socket option (and variables and files) from pre_allocated_fd to usefd.
-
- 04 Feb, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add new [set|get]sockopt ZMQ_PRE_ALLOCATED_FD to allow users to let ZMQ use a pre-allocated file descriptor instead of allocating a new one. Update [set|get]sockopt documentation and test accordingly. The main use case for this feature is a socket-activated systemd service. For more information about this feature see: http://0pointer.de/blog/projects/socket-activation.html
-
- 01 Feb, 2016 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Constantin Rack authored
Solution: Replace with `zmq_ctx_term`
-
- 08 Dec, 2015 1 commit
-
-
Ilya Kulakov authored
VMCI transport allows fast communication between the Host and a virtual machine, between virtual machines on the same host, and within a virtual machine (like IPC). It requires VMware to be installed on the host and Guest Additions to be installed on a guest.
-
- 23 Nov, 2015 1 commit
-
-
Jim Hague authored
Fixes #1646
-
- 13 Nov, 2015 2 commits
-
-
Constantin Rack authored
Solution: fix documentation
-
Constantin Rack authored
Solution: change option behaviour and adopt documentation
-
- 08 Nov, 2015 1 commit
-
-
Jens Auer authored
-
- 08 Oct, 2015 1 commit
-
-
Jens Auer authored
-
- 06 Aug, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 04 Aug, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 01 Aug, 2015 2 commits
-
-
Joe Eli McIlvain authored
-
Joe Eli McIlvain authored
-
- 31 Jul, 2015 1 commit
-
-
KIU Shueng Chuan authored
-
- 23 Jul, 2015 3 commits
-
-
KIU Shueng Chuan authored
-
KIU Shueng Chuan authored
-
Ricardo Catalinas Jiménez authored
Fixes not receiving unsubscription messages in XPUB socket with ZMQ_XPUB_VERBOSE and using a XSUB-XPUB proxy in front. This adds two modifications: - It adds a new flag, ZMQ_XPUB_VERBOSE_UNSUBSCRIBE, to enable verbose unsubscription messages, necessary when using a XSUB/XPUB proxy. - It adds a boolean switch to zmq::mtrie_t::rm () to control if the callback is invoked every time or only in the last removal. Necessary when a pipe is terminated and the verbose mode for unsubscriptions is enabled.
-
- 19 Jul, 2015 1 commit
-
-
Ricardo Catalinas Jiménez authored
-
- 08 Jul, 2015 2 commits
-
-
Juha Reunanen authored
-
Juha Reunanen authored
-
- 26 Jun, 2015 1 commit
-
-
Jonathan Reams authored
Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of ZMQ_HEARTBEAT_IVL if it's not explicitly set. Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API and round down to the nearest decisecond so that all the options are using the same units. Make the maximum heartbeat TTL match the spec (6553 seconds)
-
- 24 Jun, 2015 1 commit
-
-
Jonathan Reams authored
-
- 05 Jun, 2015 1 commit
-
-
Kapp Arnaud authored
Pull request #1426 now allow for changing the watermark after and connect() or a bind(). This patch reflect the change in the documentation. Also closes #1416.
-
- 14 Apr, 2015 2 commits
-
-
Jörg Kreuzberger authored
#1287
-
Jörg Kreuzberger authored
fix for issue #1287
-
- 26 Jan, 2015 1 commit
-
-
Julien Ruffin authored
ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription list becomes a rejection list. The PUB socket sends messages to all connected (X)SUB sockets that do not have any matching subscription. Whenever the option is used on a PUB/XPUB socket, any connecting SUB sockets must also set it or they will reject everything the publisher sends them. XSUB sockets are unaffected because they do not filter out incoming messages.
-
- 23 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Symptom is that ZMQ_STREAM sockets in 4.1.0 and 4.1.1 generate zero sized messages on each new connection, unlike 4.0.x which did not do this. Person who made this commit also changed test cases so that contract breakage did not show. Same person was later banned for persistently poor form in CZMQ contributions. Solution: enable connect notifications on ZMQ_STREAM sockets using a new ZMQ_STREAM_NOTIFY setting. By default, socket does not deliver notifications, and behaves as in 4.0.x. Fixes #1316
-
- 26 Nov, 2014 1 commit
-
-
Doron Somech authored
-
- 09 Nov, 2014 1 commit
-
-
Min RK authored
Regression in #1248 can cause lost messages at exit.
-
- 08 Nov, 2014 1 commit
-
-
J.T. Conklin authored
-