1. 28 Feb, 2016 1 commit
  2. 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
  3. 08 Feb, 2016 1 commit
  4. 04 Feb, 2016 1 commit
  5. 28 Jan, 2016 1 commit
  6. 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
  7. 23 Nov, 2015 1 commit
  8. 13 Nov, 2015 1 commit
  9. 08 Nov, 2015 1 commit
  10. 08 Oct, 2015 1 commit
  11. 06 Sep, 2015 1 commit
  12. 06 Aug, 2015 1 commit
  13. 04 Aug, 2015 1 commit
  14. 24 Jun, 2015 1 commit
  15. 05 Jun, 2015 1 commit
  16. 02 Jun, 2015 1 commit
  17. 26 Jan, 2015 1 commit
    • Julien Ruffin's avatar
      Added socket option ZMQ_INVERT_MATCHING. · cf2238f8
      Julien Ruffin authored
      ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription
      list becomes a rejection list. The PUB socket sends messages to all
      connected (X)SUB sockets that do not have any matching subscription.
      
      Whenever the option is used on a PUB/XPUB socket, any connecting SUB
      sockets must also set it or they will reject everything the publisher
      sends them. XSUB sockets are unaffected because they do not filter out
      incoming messages.
      cf2238f8
  18. 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
  19. 22 Jan, 2015 1 commit
  20. 12 Aug, 2014 1 commit
  21. 08 Aug, 2014 2 commits
  22. 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
  23. 09 May, 2014 1 commit
  24. 24 Apr, 2014 3 commits
  25. 02 Jan, 2014 1 commit
  26. 06 Dec, 2013 1 commit
    • Brandon Carpenter's avatar
      Add support for extending ZAP request address with IPC peer credentials. · a018ef5e
      Brandon Carpenter authored
      Another take on LIBZMQ-568 to allow filtering IPC connections, this time
      using ZAP.  This change is backward compatible.  If the
      ZMQ_ZAP_IPC_CREDS option is set, the user, group, and process IDs of the
      peer process are appended to the address (separated by colons) of a ZAP
      request; otherwise, nothing changes.  See LIBZMQ-568 and zmq_setsockopt
      documentation for more information.
      a018ef5e
  27. 04 Dec, 2013 1 commit
    • Brandon Carpenter's avatar
      Intial IPC accept filter support. · 8662f44e
      Brandon Carpenter authored
      Adds sets of process (Linux only), user, and group IDs for filtering
      connections from peer processes over IPC transport.  If all of the
      filter sets are empty, every connection is accepted.  Otherwise,
      credentials for a connecting process are checked against the filter sets
      and the connection is only accepted if a match is found.
      
      This commit is part of LIBZMQ-568 and only adds the filter sets and
      implements the filter in the IPC accept method.  The interface for
      adding IDs to filter sets are included in a separate commit.
      
      IPC accept filtering is supported only on Linux and OS X.
      8662f44e
  28. 25 Nov, 2013 1 commit
  29. 17 Sep, 2013 2 commits
  30. 12 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Fixed overwrite in zmq_getsockopt · 345bf146
      Pieter Hintjens authored
      On ZMQ_CURVE_xxxKEY fetches, would return 41 bytes into caller's 40-byte
      buffer. Now these fetches only return 41 bytes if the caller explicitly
      provides a 41-byte buffer (i.e. the option size is 41).
      345bf146
  31. 09 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Added ZMQ_ZAP_DOMAIN socket option · 6725c464
      Pieter Hintjens authored
      * This is passed to the ZAP handler in the 'domain' field
      
      * If not set, or empty, then NULL security does not call the ZAP handler
      
      * This resolves the phantom ZAP request syndrome seen with sockets where
        security was never intended (e.g. in test cases)
      
      * This means if you install a ZAP handler, it will not get any requests
        for new connections until you take some explicit action, which can be
        setting a username/password for PLAIN, a key for CURVE, or the domain
        for NULL.
      6725c464
  32. 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
  33. 17 Aug, 2013 1 commit
  34. 29 Jun, 2013 1 commit