1. 17 Dec, 2015 1 commit
  2. 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
  3. 30 Nov, 2015 1 commit
  4. 21 Aug, 2015 1 commit
  5. 16 Aug, 2015 1 commit
  6. 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
  7. 24 Jun, 2015 1 commit
  8. 02 Jun, 2015 1 commit
  9. 02 Feb, 2015 1 commit
  10. 01 Feb, 2015 1 commit
  11. 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
  12. 22 Jan, 2015 1 commit
  13. 09 Jan, 2015 1 commit
  14. 03 Dec, 2014 1 commit
  15. 09 Oct, 2014 1 commit
  16. 12 Sep, 2014 1 commit
  17. 11 Sep, 2014 1 commit
  18. 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
  19. 18 May, 2014 1 commit
  20. 17 May, 2014 1 commit
  21. 10 May, 2014 1 commit
  22. 30 Apr, 2014 1 commit
  23. 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
  24. 16 Mar, 2014 1 commit
  25. 15 Mar, 2014 1 commit
  26. 12 Mar, 2014 1 commit
  27. 06 Jan, 2014 2 commits
  28. 02 Jan, 2014 1 commit
  29. 03 Dec, 2013 1 commit
  30. 01 Nov, 2013 2 commits
    • Erik Hugne's avatar
      zmq: narrow condition to include TIPC in build/test · 58ac87de
      Erik Hugne authored
      As TIPC transport for 0MQ will only work on post 3.8
      Linux kernels where nonblocking connect was added,
      we add AC_RUN test to check for this functionality.
      Should the test fail, tipc is excluded from build/test.
      Signed-off-by: 's avatarErik Hugne <erik.hugne@ericsson.com>
      58ac87de
    • Erik Hugne's avatar
      zmq: add support for TIPC transport · eab85b52
      Erik Hugne authored
      A ZeroMQ application can opt for TIPC based sockets
      using the TIPC port name format:
      zmq_bind(sb, "tipc://{type,lower,upper}");
      zmq_connect(sc, "tipc://{type,inst}");
      
      'type' is the service ID, and 'lower/upper' can be
      used for service partitioning or basic load
      balancing.
      
      ZeroMQ TIPC transport requires a kernel >= 3.8
      (nonblocking connect support for TIPC).
      Signed-off-by: 's avatarErik Hugne <erik.hugne@ericsson.com>
      eab85b52
  31. 09 Oct, 2013 1 commit
  32. 04 Oct, 2013 1 commit
  33. 18 Aug, 2013 1 commit
    • Ian Barber's avatar
      Remove delay options · 531d3ebc
      Ian Barber authored
      These were exposed to users, but have subsequently been removed as
      sockopts. They are currently only being used by ZAP, so I've moved it to
      a simpl function call (actually it's only used in one case even in that,
      so there may be a further simplification possible there).
      531d3ebc
  34. 17 Aug, 2013 1 commit
  35. 29 Jun, 2013 2 commits
  36. 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
  37. 06 Jun, 2013 1 commit