1. 29 Mar, 2017 2 commits
  2. 01 Jan, 2017 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 second part · ffb31dca
      Vincent Tellier authored
       - removed the previously added encryption_error, less changes less bug
       - handshake fail is now signaled when an error happen while the
         mechanism is still hanshaking
      ffb31dca
  3. 30 Dec, 2016 1 commit
    • Vincent Tellier's avatar
      Fixed issue #2227 · b6e9e0c2
      Vincent Tellier authored
      Added two new monitoring events:
       - ZMQ_EVENT_HANDSHAKE_SUCCEED is raised once the encryption handshake succeed
       - ZMQ_EVENT_HANDSHAKE_FAILED is raised when it failed
      Both events are raised on server and client side.
      b6e9e0c2
  4. 15 May, 2016 1 commit
  5. 08 May, 2016 1 commit
  6. 21 Apr, 2016 1 commit
  7. 18 Feb, 2016 1 commit
  8. 29 Jan, 2016 2 commits
  9. 28 Jan, 2016 1 commit
  10. 27 Jan, 2016 1 commit
  11. 17 Dec, 2015 1 commit
  12. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      Ilya Kulakov authored
      VMCI transport allows fast communication between the Host
      and a virtual machine, between virtual machines on the same host,
      and within a virtual machine (like IPC).
      
      It requires VMware to be installed on the host and Guest Additions
      to be installed on a guest.
      68b13fbd
  13. 30 Nov, 2015 1 commit
  14. 21 Aug, 2015 1 commit
  15. 16 Aug, 2015 1 commit
  16. 06 Aug, 2015 1 commit
    • Soren Hansen's avatar
      Avoid terminating connections prematurely · abc845d1
      Soren Hansen authored
      While sending very large messages (far beyond what fits in a the tcp
      buffer, so it takes multiple sendto system calls for it to finish),
      zmq_close will close the connection regardless of ZMQ_LINGER.
      
      In case no engine is attached, a pipe->check_read() is needed to look
      for the delimiter in the pipe and ultimately trigger the pipe
      termination.
      
      However, if there *is* an engine attached, the check_read() looks ahead
      and finds the delimiter and terminates the connection even though the
      engine might actually still be in the middle of sending a message.
      
      This happens because while the io_thread is still busy sending the data,
      the pipe can get terminated and the io thread ends up being terminated.
      abc845d1
  17. 24 Jun, 2015 1 commit
  18. 02 Jun, 2015 1 commit
  19. 02 Feb, 2015 1 commit
  20. 01 Feb, 2015 1 commit
  21. 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
  22. 22 Jan, 2015 1 commit
  23. 09 Jan, 2015 1 commit
  24. 03 Dec, 2014 1 commit
  25. 09 Oct, 2014 1 commit
  26. 12 Sep, 2014 1 commit
  27. 11 Sep, 2014 1 commit
  28. 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
  29. 18 May, 2014 1 commit
  30. 17 May, 2014 1 commit
  31. 10 May, 2014 1 commit
  32. 30 Apr, 2014 1 commit
  33. 03 Apr, 2014 1 commit
    • Martin Hurton's avatar
      Resolve issue #939 · a53d7031
      Martin Hurton authored
      This bug is caused by fq which can terminate pipe before sending all
      frames of a message first. So sometimes two messages were mixed and this
      confused ZAP handler.
      
      This patch just modifies one pipe parameter so that socket consumes all
      messages before dropping the pipe.
      a53d7031
  34. 16 Mar, 2014 1 commit
  35. 15 Mar, 2014 1 commit
  36. 12 Mar, 2014 1 commit
  37. 06 Jan, 2014 2 commits