1. 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
  2. 26 Mar, 2017 1 commit
  3. 11 Mar, 2017 1 commit
  4. 18 Feb, 2017 1 commit
  5. 31 Dec, 2016 1 commit
  6. 30 Dec, 2016 2 commits
    • Vincent Tellier's avatar
      Code formatting + reverted hard error handshake fail · 48bc75e8
      Vincent Tellier authored
       - Moved new events in draft section + added to zmq_draft.h
       - Removed the remainning tabs
       - Reverted the hard error (back to soft error) in curve_server.cpp
      
      => The feature doesn't works anymore
      48bc75e8
    • 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
  7. 29 Dec, 2016 1 commit
  8. 05 Dec, 2016 1 commit
    • Luca Boccassi's avatar
      Problem: 4.2.0 won't compile on AIX 7.1 · 57db5f2a
      Luca Boccassi authored
      Solution: restore inclusion of poll.h if using poll before zmq.h as
      it was originally, as AIX redefines the POSIX structures and provides
      compatibility macros.
      Also add alternative aliases for 32 bit AIX's pollitem struct:
        events -> reqevents
        revents -> rtnevents
      57db5f2a
  9. 20 Nov, 2016 1 commit
  10. 08 Nov, 2016 1 commit
  11. 01 Nov, 2016 1 commit
  12. 28 Oct, 2016 2 commits
    • Luca Boccassi's avatar
      Problem: MS VC++ build broken · 2484d1c8
      Luca Boccassi authored
      Solution: try to detect architecture if building with VC++ and
      hardcode pointer size accordingly.
      Expressions are not allowed inside declspec intrinsics, which
      includes other intrinsics.
      2484d1c8
    • Luca Boccassi's avatar
      Problem: pointer union for zmq_msg_t is a hack · df367a66
      Luca Boccassi authored
      Solution: use compiler's alignment attributes instead which is
      clearer and less of a hack.
      Pointer alignment violations causing crashes on architectures
      such as sparc64 and aarch64.
      This also avoid triggering ABI checkers as the change is compatible
      even though applications that suffer from the bug should rebuild to
      take advantage of the fix.
      df367a66
  13. 27 Sep, 2016 2 commits
    • Min RK's avatar
      add n_events argument to zmq_poller_wait_all · de7fc1fc
      Min RK authored
      avoids unnecessary heap allocations, races on the number of items
      de7fc1fc
    • Min RK's avatar
      Problem: zmq_poller only signals one event · 2bc97966
      Min RK authored
      Solution: zmq_poller_wait_all signals all events
      
      allows signaling multiple events with one call to zmq_poller_wait_all
      rather than emitting only one event.
      
      this prepares for zmq_poll being based on zmq_poller,
      which requires events for all sockets rather than just one.
      2bc97966
  14. 01 Jun, 2016 1 commit
  15. 19 May, 2016 1 commit
  16. 15 May, 2016 1 commit
  17. 04 May, 2016 2 commits
    • hitstergtd's avatar
      Problem: zmq_sendiov/zmq_recviov not Deprecated · b3bb0b7f
      hitstergtd authored
      Solution:
      As preparation for 4.2 release, move the zmq_sendiov and zmq_recviov API
      methods under the Deprecated Methods section.
      
      Note: the actual methods have NOT been deprecated yet, functionally speaking
      however it is good to let API users know early. Moreover, these methods were
      not ever considered stable, at least according to src/zmq.h, and have no
      associated man pages.
      b3bb0b7f
    • Doron Somech's avatar
      ba20f665
  18. 03 May, 2016 1 commit
  19. 02 May, 2016 6 commits
  20. 01 May, 2016 1 commit
  21. 25 Apr, 2016 1 commit
  22. 24 Apr, 2016 1 commit
  23. 21 Apr, 2016 1 commit
  24. 05 Apr, 2016 1 commit
    • Jim Klimov's avatar
      Problem: including recent "zmq_utils.h" crashes gcc -pedantic jobs · d7d91713
      Jim Klimov authored
      Problem: Recent deprecation of the "zmq_utils.h" header file caused pedantic compilations (including czmq) to fail because non-portable #warning is used.
      Solution: Limit the deprecation warnings to compilers known or assumed to support the "#pragma message" (GCC, MSVC, CLANG) and wrap with GCC directives to not treat these warnings as errors on paranoid builds.
      d7d91713
  25. 29 Mar, 2016 1 commit
  26. 11 Mar, 2016 1 commit
  27. 18 Feb, 2016 1 commit
  28. 09 Feb, 2016 4 commits
    • Pieter Hintjens's avatar
      Problem: test_large_msg kills my system temporarily · 62c66ae7
      Pieter Hintjens authored
      And I'm on a reasonably sized laptop. I think allocating INT_MAX
      memory is dangerous in a test case.
      
      Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ
      and documented it and implemented the API. However I don't know how
      to get the parent context for a socket, so the code in zmq.cpp is
      still unfinished.
      62c66ae7
    • 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_XPUB_VERBOSE_UNSUBSCRIBE is clumsy · 7f6ed167
      Pieter Hintjens authored
      This option has a few issues. The name is long and clumsy. The
      functonality is not smooth: one must set both this and
      ZMQ_XPUB_VERBOSE at the same time, or things will break mysteriously.
      
      Solution: rename to ZMQ_XPUB_VERBOSER and make an atomic option.
      
      That is, implicitly does ZMQ_XPUB_VERBOSE.
      7f6ed167
    • 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