1. 27 Jan, 2020 1 commit
  2. 05 Jul, 2019 1 commit
  3. 27 May, 2018 1 commit
  4. 26 May, 2018 1 commit
  5. 18 May, 2018 1 commit
  6. 17 May, 2018 2 commits
  7. 28 Apr, 2018 1 commit
  8. 02 Feb, 2018 1 commit
  9. 08 Nov, 2017 1 commit
  10. 19 Sep, 2017 1 commit
  11. 07 Sep, 2017 1 commit
  12. 06 Sep, 2017 1 commit
  13. 27 Mar, 2017 1 commit
  14. 10 May, 2016 1 commit
  15. 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
  16. 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
  17. 18 Feb, 2016 1 commit
  18. 07 Feb, 2016 1 commit
  19. 06 Feb, 2016 1 commit
  20. 05 Feb, 2016 1 commit
  21. 28 Jan, 2016 1 commit
  22. 01 Jan, 2016 1 commit
    • Frederic Tregon's avatar
      Fixed issue #1690 (ZMQ_REQ_RELAXED) · 89417ddb
      Frederic Tregon authored
      When using ZMQ_REQ_RELAXED and a 'send' is executed after another 'send' the
      previous code would terminate the 'reply_pipe' if any.
      This is incorrect as terminating the reply pipe also terminates the send pipe
      as they are the same (a pipe associated with a socket is bidirectional).
      Doing a terminate on the pipe sets an internal flag called out_active to false
      and the pipe can no longer send messages.
      Removing the 'terminate' solves the problem. Removing this call is not an issue
      as the incorrect ordering of messages that could be incurred is taken care of
      by the ZMQ_REQ_CORRELATE option if needed.
      89417ddb
  23. 06 Sep, 2015 1 commit
  24. 02 Jun, 2015 1 commit
  25. 22 Jan, 2015 1 commit
  26. 12 Mar, 2014 1 commit
  27. 08 Jan, 2014 1 commit
  28. 02 Jan, 2014 1 commit
  29. 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
  30. 24 Aug, 2013 1 commit
    • Evan Burkitt's avatar
      get to clean compile under vs2012 · eaf227d4
      Evan Burkitt authored
      Added some missing (but existing in branch) files to libzmq11 project needed
      to compile as static library by VS2012 (at least), and fixed some warnings.
      One warning remains in raw_decoder.cpp, which I'm leaving for now because I'm
      not sure how project owners would like to fix it.
      eaf227d4
  31. 03 Aug, 2013 1 commit
  32. 29 Jul, 2013 1 commit
    • Christian Kamm's avatar
      REQ: Unset reply_pipe if it terminates. · f5c59556
      Christian Kamm authored
      * Fixes a terminate() call on a dangling pointer in the SEND_RESETS
        case.
      * Fixes recv_reply_pipe() never receiving a message once the pipe it is
        waiting on is terminated.
      f5c59556
  33. 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
  34. 26 Jul, 2013 1 commit
    • Christian Kamm's avatar
      Add ZMQ_REQ_REQUEST_IDS option. · b9646f2a
      Christian Kamm authored
      * Documentation:
      The default behavior of REQ sockets is to rely on the ordering of messages
      to match requests and responses and that is usually sufficient. When this option
      is set to 1, the REQ socket will prefix outgoing messages with an extra frame
      containing a request id. That means the full message is (request id, 0,
      user frames...). The REQ socket will discard all incoming messages that don't
      begin with these two frames.
      
      * Behavior change: When a REQ socket gets an invalid reply, it used to
        discard the message and return EAGAIN. REQ sockets still discard
        invalid messages, but keep looking at the next one automatically
        until a good one is found or there are no more messages.
      * Add test_req_request_ids.
      b9646f2a
  35. 14 Jul, 2013 1 commit
    • Christian Kamm's avatar
      REQ sockets drop replies from unasked peers. · c56d797b
      Christian Kamm authored
      * Add lb_t::sendpipe() that returns the pipe that was used for sending,
        similar to fq_t::recvpipe().
      * Add forwarder functions to dealer_t to access these two.
      * Add logic to req_t to ignore replies on pipes that are not the one
        where the request was sent.
      * Enable test in test_spec_req.
      c56d797b
  36. 29 Jun, 2013 2 commits
  37. 11 Apr, 2013 1 commit
  38. 12 Mar, 2013 1 commit
    • Pieter Hintjens's avatar
      Removed corporate advertisements from source file headers · f0f16505
      Pieter Hintjens authored
      Copyrights had become ads for Sustrik's corporate sponsors, going against the original
      agreement to share copyrights with the community (that agreement was: one line stating
      iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads
      is also unfair to the many individual authors. I've removed ALL corporate title from
      the source files so the copyright statements can now be centralized in AUTHORS and
      source files can be properly updated on an annual basis.
      f0f16505