1. 21 Nov, 2016 1 commit
  2. 20 Nov, 2016 1 commit
  3. 16 Nov, 2016 1 commit
  4. 07 Oct, 2016 1 commit
  5. 03 Oct, 2016 1 commit
  6. 25 Sep, 2016 1 commit
  7. 21 Sep, 2016 1 commit
  8. 13 Aug, 2016 1 commit
    • KIU Shueng Chuan's avatar
      Problem: zmq_stream doc is confusing regarding ZMQ_SNDMORE flag · 53402156
      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.
      53402156
  9. 03 Jun, 2016 1 commit
  10. 01 May, 2016 1 commit
    • hitstergtd's avatar
      Problem: zmq_setsockopt(3) man page formatting · 4809926c
      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
      4809926c
  11. 29 Apr, 2016 1 commit
  12. 04 Apr, 2016 1 commit
  13. 20 Mar, 2016 1 commit
    • Frederic Tregon's avatar
      Fixed issue #1695 (ZMQ_REQ_CORRELATE) · e45dfe3b
      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.
      e45dfe3b
  14. 06 Mar, 2016 1 commit
    • Luca Boccassi's avatar
      Problem: doc/Makefile.am ignores --without-docs · 4366d7ed
      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.
      4366d7ed
  15. 09 Feb, 2016 6 commits
    • Pieter Hintjens's avatar
      Problem: test_large_msg kills my system temporarily · 62c66ae7
      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.
      62c66ae7
    • Pieter Hintjens's avatar
      Problem: ZMQ_TCP_RECV_BUFFER/SEND_BUFFER are redundant · 7470c00d
      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.
      7470c00d
    • Pieter Hintjens's avatar
      Problem: zmq_getsockopt wrongly referred to ZMQ_THREADSAFE · 884c7f78
      Pieter Hintjens authored
      The proper name is ZMQ_THREAD_SAFE
      
      Solution: fix in the documentation.
      884c7f78
    • Pieter Hintjens's avatar
      Problem: ZMQ_XPUB_VERBOSE_UNSUBSCRIBE is clumsy · 7f6ed167
      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.
      7f6ed167
    • Pieter Hintjens's avatar
      Problem: ZMQ_TCP_RETRANSMIT_TIMEOUT is a clumsy name · da8ce55a
      Pieter Hintjens authored
      Solution: rename to ZMQ_MAXRT
      
      This is the option name used on Windows, so easier to use and
      remember.
      da8ce55a
    • Luca Boccassi's avatar
      Problem: ZMQ_USEFD does not follow conventions · edc4ee03
      Luca Boccassi authored
      Solution: rename socket option (and variables and files) from usefd
      to use_fd.
      edc4ee03
  16. 08 Feb, 2016 1 commit
  17. 06 Feb, 2016 1 commit
  18. 04 Feb, 2016 1 commit
  19. 01 Feb, 2016 3 commits
  20. 29 Dec, 2015 1 commit
  21. 14 Dec, 2015 1 commit
  22. 09 Dec, 2015 1 commit
  23. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      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.
      68b13fbd
  24. 23 Nov, 2015 1 commit
  25. 13 Nov, 2015 2 commits
  26. 08 Nov, 2015 1 commit
  27. 08 Oct, 2015 1 commit
  28. 18 Sep, 2015 1 commit
  29. 14 Sep, 2015 1 commit
    • Elliot Saba's avatar
      Fix pointer indirection precedence issue in docs · 1fbc67a4
      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.
      1fbc67a4
  30. 13 Sep, 2015 1 commit
  31. 11 Sep, 2015 2 commits