- 21 Nov, 2016 1 commit
-
-
Richard Janis Goldschmidt authored
-
- 20 Nov, 2016 1 commit
-
-
Luca Boccassi authored
Solution: mention it in zmq_ctx_get manpage
-
- 16 Nov, 2016 1 commit
-
-
Andreas Rottmann authored
This addresses #2169.
-
- 07 Oct, 2016 1 commit
-
-
Thomas Braun authored
Solution: Fix it.
-
- 03 Oct, 2016 1 commit
-
-
WGH authored
-
- 25 Sep, 2016 1 commit
-
-
Patrik Wenger authored
-
- 21 Sep, 2016 1 commit
-
-
Patrik Wenger authored
The effect can be seen on http://api.zeromq.org/4-2:zmq-getsockopt at options ZMQ_USE_FD and ZMQ_RATE. Solution: fix length of squiggly line under option title
-
- 13 Aug, 2016 1 commit
-
-
KIU Shueng Chuan authored
Solution: fix it. The documentation first states that the ZMQ_SNDMORE flag is ignored on data frames. Then it states that omitting the ZMQ_SNDMORE flag has consequences. The example HTTP server code further muddies the situation with a similar comment. The implementation of ZMQ_STREAM only accepts two-part messages. The first part is an identity frame while the second and last part is the data frame. As with any multipart message, all parts except the last need the ZMQ_SNDMORE flag. The second and last part would normally omit the ZMQ_SNDMORE flag to mark the end of the multipart message. However, the ZMQ_STREAM implementation ignores the ZMQ_SNDMORE flag on the data frame rather than requiring that it be omitted. The latter behaviour would have been more consistent with the other ZeroMQ sockets.
-
- 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
-
- 29 Apr, 2016 1 commit
-
-
somdoron authored
-
- 04 Apr, 2016 1 commit
-
-
Pieter Hintjens authored
It says that ZMQ_SERVER never blocks; whereas it does block on sending to a client whose pipe is full. Solution: fix it.
-
- 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.
-
- 06 Mar, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add the document files to the MAN_DOC and MAN_HTML targets in doc/Makefile.am only if BUILD_DOC and INSTALL_MAN are set, otherwise leave the targets empty to avoid errors in make distcheck.
-
- 09 Feb, 2016 6 commits
-
-
Pieter Hintjens authored
And I'm on a reasonably sized laptop. I think allocating INT_MAX memory is dangerous in a test case. Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ and documented it and implemented the API. However I don't know how to get the parent context for a socket, so the code in zmq.cpp is still unfinished.
-
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
The proper name is ZMQ_THREAD_SAFE Solution: fix in the documentation.
-
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.
-
- 06 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
Solution: be more explicit in the code, and in the zmq_recv man page (which is the most unobvious case). Assert if length is not zero and buffer is nonetheless null.
-
- 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`
-
- 29 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
These sockets don't handle multipart data, so if callers send it, they drop frames, and things break silently. Solution: if the caller tries to use ZMQ_SNDMORE, return -1 and set errno to EINVAL.
-
- 14 Dec, 2015 1 commit
-
-
Ilya Kulakov authored
-
- 09 Dec, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: fix this.
-
- 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
-
- 18 Sep, 2015 1 commit
-
-
maurice barnum authored
-
- 14 Sep, 2015 1 commit
-
-
Elliot Saba authored
Without this change, a segmentation fault is likely to occur when using the proposed snippet of code, as `*address[size]` is equivalent to `*(address[size])`, not `(*address)[size]` as clearly intended.
-
- 13 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
- both are thread safe - they do not accept ZMQ_SNDMORE nor ZMQ_RCVMORE
-
- 11 Sep, 2015 2 commits
-
-
Pieter Hintjens authored
REQ-REP barely work, and DEALER-ROUTER are misnamed. As we move to formalizing CLIENT-SERVER, we can deprecate request-reply. Solution: move this section to the end of the man page, and mark as "will be deprecated".
-
Pieter Hintjens authored
Solution: add man pages/sections for: * ZMQ_SERVER * ZMQ_CLIENT * ZMQ_THREADSAFE * zmq_msg_routing_id * zmq_msg_set_routing_id
-