1. 30 Nov, 2015 1 commit
  2. 18 Nov, 2015 1 commit
  3. 08 Nov, 2015 1 commit
  4. 08 Oct, 2015 1 commit
  5. 21 Aug, 2015 1 commit
  6. 16 Aug, 2015 1 commit
  7. 23 Jul, 2015 1 commit
  8. 26 Jun, 2015 1 commit
    • Jonathan Reams's avatar
      Fix units and default values for heartbeats options · e9a5bc8d
      Jonathan Reams authored
      Set the ZMQ_HEARTBEAT_TIMEOUT to default to the value of
      ZMQ_HEARTBEAT_IVL if it's not explicitly set.
      Change the units of ZMQ_HEARTBEAT_TTL to milliseconds in the API
      and round down to the nearest decisecond so that all the options
      are using the same units.
      Make the maximum heartbeat TTL match the spec (6553 seconds)
      e9a5bc8d
  9. 24 Jun, 2015 1 commit
  10. 14 Jun, 2015 1 commit
    • Jens Auer's avatar
      Fixed wrong buffer end detection in v2_decoder. · dfe19080
      Jens Auer authored
      zero-copy msg_t::init cannot be used when the message exceeds either
      the buffer end or the last received byte. To detect this, the buffer
      is now resized to the numnber of received bytes.
      dfe19080
  11. 02 Jun, 2015 1 commit
  12. 19 May, 2015 1 commit
  13. 22 Apr, 2015 1 commit
  14. 19 Feb, 2015 2 commits
  15. 18 Feb, 2015 1 commit
  16. 27 Jan, 2015 1 commit
  17. 23 Jan, 2015 1 commit
    • Pieter Hintjens's avatar
      Problem: commit afb24b53 broke ZMQ_STREAM contract · 6ced7027
      Pieter Hintjens authored
      Symptom is that ZMQ_STREAM sockets in 4.1.0 and 4.1.1 generate zero
      sized messages on each new connection, unlike 4.0.x which did not do
      this.
      
      Person who made this commit also changed test cases so that contract
      breakage did not show. Same person was later banned for persistently
      poor form in CZMQ contributions.
      
      Solution: enable connect notifications on ZMQ_STREAM sockets using a
      new ZMQ_STREAM_NOTIFY setting. By default, socket does not deliver
      notifications, and behaves as in 4.0.x.
      
      Fixes #1316
      6ced7027
  18. 22 Jan, 2015 1 commit
  19. 16 Jan, 2015 3 commits
  20. 19 Dec, 2014 1 commit
    • Pieter Hintjens's avatar
      Problem: very hard to debug security mechanism mismatch · 17937ffc
      Pieter Hintjens authored
      E.g. when server is not configured, and client tries PLAIN security,
      there is no hint of why this does not work.
      
      Solution: add debugging output for this case. Note that the various
      debugging outputs for security failures should probably be sent to
      an inproc monitor of some kind.
      17937ffc
  21. 03 Dec, 2014 2 commits
  22. 09 Oct, 2014 2 commits
  23. 19 Sep, 2014 1 commit
  24. 03 Jul, 2014 1 commit
  25. 22 Jun, 2014 1 commit
    • Martin Hurton's avatar
      Add support for SOCKS proxies · f06ca69a
      Martin Hurton authored
      This is still raw and experimental.
      To connect through a SOCKS proxy, set ZMQ_SOCKS_PROXY socket option on
      socket before issuing a connect call, e.g.:
      
          zmq_setsockopt (s, ZMQ_SOCKS_PROXY,
              "127.0.0.1:22222", strlen ("127.0.0.1:22222"));
          zmq_connect (s, "tcp://127.0.0.1:5555");
      
      Known limitations:
      - only SOCKS version 5 supported
      - authentication not supported
      - new option is still undocumented
      f06ca69a
  26. 18 May, 2014 1 commit
  27. 17 May, 2014 1 commit
  28. 12 May, 2014 1 commit
  29. 09 May, 2014 1 commit
  30. 07 May, 2014 1 commit
    • Martin Hurton's avatar
      NULL: Implement ERROR handling · 934560b5
      Martin Hurton authored
      NULL mechanism sends ERROR command rather than READY command when ZAP
      handler rejects the ZAP request (status code != "200"). The body of
      ERROR command contains the status code as returned by ZAP handler.
      934560b5
  31. 06 May, 2014 1 commit
  32. 05 May, 2014 1 commit
  33. 03 May, 2014 1 commit
  34. 02 May, 2014 2 commits