1. 01 Nov, 2013 3 commits
  2. 29 Oct, 2013 2 commits
  3. 28 Oct, 2013 2 commits
  4. 18 Oct, 2013 1 commit
  5. 04 Oct, 2013 1 commit
  6. 26 Sep, 2013 1 commit
  7. 20 Sep, 2013 2 commits
    • 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
    • Pieter Hintjens's avatar
      Renamed test_connect_delay to test_immediate · 92c01f69
      Pieter Hintjens authored
      * The ZMQ_CONNECT_DELAY option was renamed to ZMQ_IMMEDIATE
      92c01f69
  8. 19 Sep, 2013 1 commit
  9. 12 Sep, 2013 1 commit
  10. 11 Sep, 2013 1 commit
  11. 10 Sep, 2013 1 commit
  12. 04 Sep, 2013 5 commits
  13. 02 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Fixed 'make check' failures · fba56120
      Pieter Hintjens authored
      - Split off NULL security check from PLAIN
      - Cleaned up test_linger code a little
      - Got all tests to pass, added TODOs for outstanding issues
      - Added ZAP authentication for NULL test case
      - NULL mechanism was not passing server identity - fixed
      - cleaned up test_security_plain and removed option double-checks (made code ugly)
      - lowered timeout on expect_bounce_fail to 150 msec to speed up checks
      - removed all sleeps from test_fork and simplified code (it still passes :-)
      fba56120
  14. 01 Sep, 2013 2 commits
  15. 19 Aug, 2013 1 commit
  16. 03 Aug, 2013 1 commit
  17. 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
  18. 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
  19. 05 Jul, 2013 1 commit
  20. 02 Jul, 2013 1 commit
    • Christian Kamm's avatar
      Add tests for Request-Reply pattern sockets. · 798b3940
      Christian Kamm authored
      * See http://rfc.zeromq.org/spec:28/REQREP
      * Not all testable statements are covered.
      * At this point, there are several failures:
        - test_spec_req: The REQ socket does not correctly discard messages
          from peers that are not currently being talked to.
        - test_spec_dealer/router: On disconnect, the queues seem to not be
          emptied. The DEALER can still receive a message the disconnected
          peer sent, the ROUTER can still send to the identity of the dis-
          connected peer.
      798b3940
  21. 28 Jun, 2013 1 commit
  22. 27 Jun, 2013 1 commit
    • Pieter Hintjens's avatar
      Added ZMQ_STREAM socket type · ad779379
      Pieter Hintjens authored
      - designed for TCP clients and servers
      - added HTTP client / server example in tests/test_stream.cpp
      - same as ZMQ_ROUTER + ZMQ_ROUTER_RAW + ZMQ_ROUTER_MANDATORY
      - includes b893ce set ZMQ_IDENTITY on outgoing connect
      - deprecates ZMQ_ROUTER_RAW
      ad779379
  23. 22 Jun, 2013 1 commit
  24. 05 Jun, 2013 2 commits
  25. 15 May, 2013 1 commit
    • Pieter Hintjens's avatar
      Added configuration for PLAIN security · e1f797b0
      Pieter Hintjens authored
      * ZMQ_PLAIN_SERVER, ZMQ_PLAIN_USERNAME, ZMQ_PLAIN_PASSWORD options
      * Man page changes to zmq_setsockopt and zmq_getsockopt
      * Man pages for ZMQ_NULL, ZMQ_PLAIN, and ZMQ_CURVE
      * Test program test_security
      e1f797b0
  26. 27 Apr, 2013 1 commit
  27. 25 Apr, 2013 1 commit
    • Jon Dyte's avatar
      Experimental function zmq_recviov doesnt work correctly in a couple of cases · 56ead844
      Jon Dyte authored
      1) VSM - you cannot hand out the 'data' address as it was not allocated on the heap
      2) for other messages the 'data' address cannot be handed out either, as it not the address
      originally returned by malloc and hence cannot be passed to 'free'.
      see msg.cpp
      u.lmsg.content = (content_t*) malloc (sizeof (content_t) + size_);
      ....
      u.lmsg.content->data = u.lmsg.content + 1;
      
      So the function is changed to always malloc a data buffer and copy the data into it.
      There is a possible optimisation using memmove for the non-VSM case but that is not done yet.
      56ead844
  28. 07 Feb, 2013 1 commit
  29. 31 Jan, 2013 1 commit