1. 09 Feb, 2020 1 commit
  2. 05 Feb, 2020 1 commit
  3. 26 Jan, 2020 1 commit
  4. 23 Sep, 2019 1 commit
  5. 12 Apr, 2019 1 commit
  6. 21 Jun, 2018 1 commit
  7. 23 Apr, 2018 1 commit
  8. 19 Sep, 2017 2 commits
  9. 07 Sep, 2017 3 commits
  10. 19 Aug, 2017 1 commit
  11. 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
  12. 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
  13. 23 Feb, 2017 1 commit
  14. 07 Oct, 2016 1 commit
  15. 03 Oct, 2016 1 commit
  16. 13 Aug, 2016 1 commit
    • KIU Shueng Chuan's avatar
      Problem: zmq_stream doc is confusing regarding ZMQ_SNDMORE flag · 53402156
      KIU Shueng Chuan authored
      Solution: fix it.
      
      The documentation first states that the ZMQ_SNDMORE flag is ignored on
      data frames. Then it states that omitting the ZMQ_SNDMORE flag has
      consequences. The example HTTP server code further muddies the situation
      with a similar comment.
      
      The implementation of ZMQ_STREAM only accepts two-part messages.
      The first part is an identity frame while the second and last part is
      the data frame.
      
      As with any multipart message, all parts except the last need the
      ZMQ_SNDMORE flag. The second and last part would normally omit the
      ZMQ_SNDMORE flag to mark the end of the multipart message.
      
      However, the ZMQ_STREAM implementation ignores the ZMQ_SNDMORE flag on
      the data frame rather than requiring that it be omitted. The latter
      behaviour would have been more consistent with the other ZeroMQ
      sockets.
      53402156
  17. 29 Apr, 2016 1 commit
  18. 04 Apr, 2016 1 commit
  19. 13 Sep, 2015 1 commit
  20. 11 Sep, 2015 2 commits
  21. 22 May, 2015 1 commit
  22. 26 Apr, 2014 1 commit
  23. 24 Feb, 2014 1 commit
    • Olaf Mandel's avatar
      Fix zmq_socket example in documentation · 45dfbc52
      Olaf Mandel authored
      Issues adressed:
       - The actual data was never read from the socket, causing all even
         numbered loop iterations to fail
       - The socket variable was called server once
      45dfbc52
  24. 15 Jan, 2014 1 commit
    • Andre Caron's avatar
      Adds support for detecting ZMQ_STREAM disconnections. · 17651b92
      Andre Caron authored
      When a ZMQ_STREAM socket connection is broken (intentionally, via `shutdown()`
      or accidentally via client crash or network failure), there is no way for the
      application to dertermine that it should drop per-connection data (such as
      buffers).
      
      This contribution makes sure the application receives a 0-length message to
      notify it that the connection has been broken.  This is symmetric with the
      process of closing the connection from within the application (where the
      application sends a 0-length message to tell ZeroMQ to close the connection).
      
      Conflicts:
      	CMakeLists.txt
      17651b92
  25. 23 Dec, 2013 1 commit
  26. 13 Nov, 2013 1 commit
  27. 04 Sep, 2013 1 commit
  28. 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
  29. 07 Jun, 2013 1 commit
  30. 05 Jun, 2013 1 commit
  31. 15 Apr, 2013 1 commit
  32. 08 Jan, 2013 1 commit
  33. 09 Nov, 2012 1 commit
  34. 07 Nov, 2012 1 commit
  35. 27 Oct, 2012 1 commit
  36. 04 Jul, 2012 1 commit