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. 28 Jan, 2016 1 commit
  3. 02 Jun, 2015 1 commit
  4. 22 Jan, 2015 1 commit
  5. 02 Jan, 2014 1 commit
  6. 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
  7. 18 Sep, 2013 1 commit
  8. 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
  9. 17 Aug, 2013 1 commit
  10. 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