1. 23 Nov, 2017 1 commit
  2. 16 Nov, 2017 1 commit
  3. 10 Nov, 2017 1 commit
  4. 25 Oct, 2017 1 commit
    • f18m's avatar
      Change ZMQ_THREAD_AFFINITY to… · 2aa0e6fd
      f18m authored
      Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
      2aa0e6fd
  5. 21 Oct, 2017 1 commit
  6. 18 Oct, 2017 1 commit
  7. 17 Oct, 2017 5 commits
  8. 16 Oct, 2017 2 commits
  9. 09 Oct, 2017 1 commit
  10. 19 Sep, 2017 4 commits
  11. 07 Sep, 2017 4 commits
  12. 20 Aug, 2017 1 commit
  13. 19 Aug, 2017 1 commit
  14. 18 Aug, 2017 1 commit
  15. 17 Aug, 2017 1 commit
    • Min RK's avatar
      specify that groups shall be UTF8 · 3130b913
      Min RK authored
      group being a `char *` is logically a text type, which needs an encoding.
      
      Declare in the API that groups shall be UTF8-encoded,
      matching the `zmq_msg_gets` API, which is the other user-facing `char *` API,
      which has the same definition.
      
      This allows bindings to provide text-type APIs,
      which they cannot do if arbitrary bytes are allowed
      3130b913
  16. 04 Aug, 2017 2 commits
  17. 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
  18. 14 Jul, 2017 1 commit
    • Marc Sune's avatar
      Problem: adapt, clarify docs ZMQ_ROUTER_MANDATORY · 609c1312
      Marc Sune authored
      Solution:
      
      * Document the new behaviour when generating 'ZMQ_POLLOUT' events
        for ZMQ_ROUTER sockets with 'ZMQ_ROUTER_MANDATORY' set to `1`
      * Add clarifications for 'ZMQ_ROUTER' socket when
        'ZMQ_ROUTER_MANDATORY' is set to `1`
      609c1312
  19. 23 Jun, 2017 1 commit
  20. 24 Apr, 2017 1 commit
  21. 21 Apr, 2017 2 commits
  22. 20 Apr, 2017 1 commit
    • Jim Garlick's avatar
      gssapi: document ZMQ_GSSAPI_PRINCIPAL as optional · c371824b
      Jim Garlick authored
      Problem: the ZMQ_GSSAPI_PRINCIPAL socket option is described
      as mandatory in the zmq_gssapi(7) manual page.  In fact it
      is optional.
      
      Solution: Describe ZMQ_GSSAPI_PRINCIPAL as optional.
      If unspecified, default credentials are used.
      c371824b
  23. 23 Feb, 2017 1 commit
  24. 19 Jan, 2017 2 commits
  25. 03 Jan, 2017 2 commits