1. 02 Feb, 2019 1 commit
  2. 15 Aug, 2018 2 commits
  3. 30 May, 2018 1 commit
  4. 26 May, 2018 1 commit
  5. 22 May, 2018 1 commit
  6. 18 May, 2018 1 commit
  7. 13 May, 2018 1 commit
  8. 10 May, 2018 1 commit
  9. 14 Mar, 2018 1 commit
    • Pontus Sköldström's avatar
      Support application metadata through ZMQ_METADATA · dd5eec35
      Pontus Sköldström authored
      Lets the application set per-connection metadata.
      Metadata is specified as "X-key:value" and set using zmq_setsockopt, eg:
      zmq_setsockopt (s, ZMQ_METADATA, "X-key:value", 11);
      
      The peer can then obtain the metadata from a received message:
      char *data = zmq_msg_gets(msg, "X-key");
      dd5eec35
  10. 06 Mar, 2018 1 commit
  11. 05 Mar, 2018 1 commit
    • Stefan Kaes's avatar
      Problem: enormous memory increase due to zero copy decoding · fcbd2a57
      Stefan Kaes authored
      The zero copy decoding strategy implemented for 4.2.0 can lead to a large
      increase of main memory usage in some cases (I have seen one program go up to
      40G from 10G after upgrading from 4.1.4). This commit adds a new option to
      contexts, called ZMQ_ZERO_COPY_RECV, which allows one to switch to the old
      decoding strategy.
      fcbd2a57
  12. 09 Feb, 2018 1 commit
  13. 08 Feb, 2018 1 commit
  14. 02 Feb, 2018 1 commit
  15. 18 Oct, 2017 1 commit
  16. 09 Oct, 2017 2 commits
  17. 19 Sep, 2017 2 commits
  18. 07 Sep, 2017 1 commit
  19. 06 Sep, 2017 1 commit
  20. 31 Jul, 2017 1 commit
    • Brian Russell's avatar
      Add socket option BINDTODEVICE · b963542e
      Brian Russell authored
      Linux now supports Virtual Routing and Forwarding (VRF) as per:
      
      https://www.kernel.org/doc/Documentation/networking/vrf.txt
      
      In order for an application to bind or connect to a socket with an
      address in a VRF, they need to first bind the socket to the VRF device:
      
          setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1);
      
      Note "dev" is the VRF device, eg. VRF "blue", rather than an interface
      enslaved to the VRF.
      
      Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device.
      In general, if a socket is bound to a device, eg. an interface, only
      packets received from that particular device are processed by the socket.
      
      If device is a VRF device, then subsequent binds/connects to that socket
      use addresses in the VRF routing table.
      b963542e
  21. 25 Apr, 2017 1 commit
    • Jim Garlick's avatar
      gssapi: drop unnecessary ifdefs · 53918fc1
      Jim Garlick authored
      Problem: GSSAPI DRAFT code was made conditional on
      ZMQ_BUILD_DRAFT_API, but zmq_draft.h duplicates the DRAFT
      symbols definitions from zmq.h so this is unnecessary.
      
      Solution: drop the extra ifdefs
      53918fc1
  22. 24 Apr, 2017 1 commit
    • Jim Garlick's avatar
      gssapi: move new options to DRAFT section · 9fbf2e2e
      Jim Garlick authored
      Problem: The new GSSAPI NAMESPACE options should have been
      added to the DRAFT section of the API so they can be changed
      until stabilized.
      
      Solution:
      - Move defines to the DRAFT section of zmq.h
      - Duplicate them in zmq_draft.h, as is the local custom
      - Compile only if defined (ZMQ_BUILD_DRAFT_API)
      - Refactor internals slightly to avoid #ifdef hell
      9fbf2e2e
  23. 21 Apr, 2017 1 commit
    • Jim Garlick's avatar
      gssapi: add NAMETYPE socket options · 0b185e82
      Jim Garlick authored
      Problem: principals are looked up unconditionally
      with the GSS_C_NT_HOSTBASED_SERVICE name type.
      
      Solution: Add two new socket options to set the name type
      for ZMQ_GSSAPI_PRINCIPAL and ZMQ_GSSAPI_SERVICE_PRINCIPAL:
      
      ZMQ_GSSAPI_PRINCIPAL_NAMETYPE
      ZMQ_GSSAPI_SERVICE_PRINCIPAL_NAMETYPE
      
      They take an integer argument which must be one of
      ZMQ_GSSAPI_NT_HOSTBASED (0) - default
      ZMQ_GSSAPI_NT_USER_NAME (1)
      ZMQ_GSSAPI_NT_KRB5_PRINCIPAL (2)
      
      These correspond to GSSAPI name types of:
      GSS_C_NT_HOSTBASED_SERVICE
      GSS_C_NT_USER_NAME
      GSS_KRB5_NT_PRINCIPAL_NAME
      
      Fixes #2542
      0b185e82
  24. 19 Dec, 2016 1 commit
  25. 16 Dec, 2016 2 commits
  26. 14 May, 2016 1 commit
  27. 28 Feb, 2016 1 commit
  28. 09 Feb, 2016 3 commits
    • Pieter Hintjens's avatar
      Problem: ZMQ_TCP_RECV_BUFFER/SEND_BUFFER are redundant · 7470c00d
      Pieter Hintjens authored
      These options are confusing and redundant. Their names suggest
      they apply to the tcp:// transport, yet they are used for all
      stream protocols. The methods zmq::set_tcp_receive_buffer and
      zmq::set_tcp_send_buffer don't use these values at all, they use
      ZMQ_SNDBUF and ZMQ_RCVBUF.
      
      Solution: merge these new options into ZMQ_SNDBUF and ZMQ_RCVBUF.
      
      This means defaulting these two options to 8192, and removing the
      new options. We now have ZMQ_SNDBUF and ZMQ_RCVBUF being used both
      for TCP socket control, and for input/output buffering.
      
      Note: the default for SNDBUF and RCVBUF are otherwise 4096.
      7470c00d
    • Pieter Hintjens's avatar
      Problem: ZMQ_TCP_RETRANSMIT_TIMEOUT is a clumsy name · da8ce55a
      Pieter Hintjens authored
      Solution: rename to ZMQ_MAXRT
      
      This is the option name used on Windows, so easier to use and
      remember.
      da8ce55a
    • Luca Boccassi's avatar
      Problem: ZMQ_USEFD does not follow conventions · edc4ee03
      Luca Boccassi authored
      Solution: rename socket option (and variables and files) from usefd
      to use_fd.
      edc4ee03
  29. 08 Feb, 2016 1 commit
  30. 04 Feb, 2016 1 commit
  31. 28 Jan, 2016 1 commit
  32. 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
  33. 23 Nov, 2015 1 commit
  34. 13 Nov, 2015 1 commit