1. 02 Apr, 2016 1 commit
    • Frederic Tregon's avatar
      Fixed ZMQ_REQ_CORRELATE (see pull request #1730) · 625b6187
      Frederic Tregon authored
      Problem: Since pull request #1730 was merged, protocol for REQ socket is
      checked at the session level and this check does not take into account
      the possibility of a request_id being part of the message. Thus the option
      ZMQ_REQ_CORRELATE would no longer work.
      This is now fixed: the possiblity of a 4 bytes integer being present
      before the delimiter frame is taken into account (whether or not this
      breaks the REQ/REP RFC is another issue).
      625b6187
  2. 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
  3. 13 Feb, 2016 1 commit
  4. 28 Jan, 2016 2 commits
  5. 03 Jan, 2016 1 commit
  6. 02 Jun, 2015 1 commit
  7. 30 Jan, 2015 1 commit
  8. 22 Jan, 2015 1 commit
  9. 02 Jan, 2014 1 commit
  10. 06 Nov, 2013 1 commit
    • Pieter Hintjens's avatar
      Removed over-long pauses in tests · 5b60540e
      Pieter Hintjens authored
      - used msleep (10) in most places instead of zmq_sleep (1)
      - may cause failures on slower machines
      - to change, modify SETTLE_TIME in testutil.h
      - tested down to 1 msec on fast boxes
      5b60540e
  11. 20 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Renamed new socket options to be clearer · 5e609be3
      Pieter Hintjens authored
      * ZMQ_REQ_STRICT was negative option (default 1) which goes against
        the standard, where defaults are zero. I renamed this to
        ZMQ_REQ_RELAXED.
      
      * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution
        rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE
        which seems more explicit.
      5e609be3
  12. 18 Sep, 2013 1 commit
  13. 15 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added z85 codec to ZMQ API · 576e3ca5
      Pieter Hintjens authored
      * Removed redundant Z85 code and include files from project
      * Simplified use of headers in test cases (now they all just use testutil.hpp)
      * Export zmq_z85_encode() and zmq_z85_decode() in API
      * Added man pages for these two functions
      576e3ca5
  14. 17 Aug, 2013 1 commit
  15. 03 Aug, 2013 1 commit
  16. 28 Jul, 2013 1 commit
    • Christian Kamm's avatar
      Add ZMQ_REQ_SEND_RESETS option. · a0cc87a9
      Christian Kamm authored
      This allows making a new request on a REQ socket by sending a new
      message. Without the option set, calling send() after the first message
      is done will continue to return an EFSM error.
      
      It's useful for when a REQ is not getting a response. Previously that
      meant creating a new socket or switching to DEALER.
      a0cc87a9