- 09 Feb, 2020 1 commit
-
-
Doron Somech authored
Solution: a new socket type, called PEER. Very similar to SERVER, but can only connect to other PEERs. Also a new zmq_connect_peer method, that connect and return a routing-id in thread-safe and atomic operation
-
- 05 Feb, 2020 1 commit
-
-
Doron Somech authored
-
- 26 Jan, 2020 1 commit
-
-
Simon Giesecke authored
Solution: fix handling of _starting and _terminate flags Add tests for this situation. Clarify documentation of zmq_ctx_shutdown and zmq_socket. Fixes #3792
-
- 23 Sep, 2019 1 commit
-
-
trya authored
Solution: Reflect real behavior of sockets blocking on send operations Sockets that block in mute state only block when no peer is available if the transport is connection-oriented and the ZMQ_IMMEDIATE socket option is set.
-
- 12 Apr, 2019 1 commit
-
-
Luca Boccassi authored
Solution: fix it
-
- 21 Jun, 2018 1 commit
-
-
jamesdillonharvey authored
* update pair doc
-
- 23 Apr, 2018 1 commit
-
-
Luca Boccassi authored
Solution: add note like for radio-dish Fixes: #3050
-
- 19 Sep, 2017 2 commits
- 07 Sep, 2017 3 commits
-
-
Doron Somech authored
-
sigiesec authored
Solution: use "routing_id" instead
-
sigiesec authored
Solution: change docs to refer to "Routing id"
-
- 19 Aug, 2017 1 commit
-
-
Luca Boccassi authored
Solution: as discussed, remove the deprecation notices, as many users expressed the need for multi-part support. Fixes #2699
-
- 17 Aug, 2017 1 commit
-
-
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
-
- 14 Jul, 2017 1 commit
-
-
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`
-
- 23 Feb, 2017 1 commit
-
-
Takeshi Abe authored
Solution: fix it
-
- 07 Oct, 2016 1 commit
-
-
Thomas Braun authored
Solution: Fix it.
-
- 03 Oct, 2016 1 commit
-
-
WGH authored
-
- 13 Aug, 2016 1 commit
-
-
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.
-
- 29 Apr, 2016 1 commit
-
-
somdoron authored
-
- 04 Apr, 2016 1 commit
-
-
Pieter Hintjens authored
It says that ZMQ_SERVER never blocks; whereas it does block on sending to a client whose pipe is full. Solution: fix it.
-
- 13 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
- both are thread safe - they do not accept ZMQ_SNDMORE nor ZMQ_RCVMORE
-
- 11 Sep, 2015 2 commits
-
-
Pieter Hintjens authored
REQ-REP barely work, and DEALER-ROUTER are misnamed. As we move to formalizing CLIENT-SERVER, we can deprecate request-reply. Solution: move this section to the end of the man page, and mark as "will be deprecated".
-
Pieter Hintjens authored
Solution: add man pages/sections for: * ZMQ_SERVER * ZMQ_CLIENT * ZMQ_THREADSAFE * zmq_msg_routing_id * zmq_msg_set_routing_id
-
- 22 May, 2015 1 commit
-
-
Diego Fons authored
-
- 26 Apr, 2014 1 commit
-
-
KIU Shueng Chuan authored
Also the portion about how to close a connection does not only apply to servers.
-
- 24 Feb, 2014 1 commit
-
-
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
-
- 15 Jan, 2014 1 commit
-
-
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
-
- 23 Dec, 2013 1 commit
-
-
KIU Shueng Chuan authored
-
- 13 Nov, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 04 Sep, 2013 1 commit
-
-
Sebastien Pierre authored
-
- 27 Jun, 2013 1 commit
-
-
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
-
- 07 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
- REQ and REP sockets don't have HWM issues - ZMQ_DONTWAIT applies to DEALER and PUSH only
-
- 05 Jun, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 15 Apr, 2013 1 commit
-
-
Pieter Hintjens authored
contributors and doesn't reflect the real process. I've taken out all named authors and referred to the contribution policy. Hopefully this will improve the contributions to the man pages.
-
- 08 Jan, 2013 1 commit
-
-
John Muehlhausen authored
zmq::xpub_t::xread_activated() – change to process messages without 0 or 1 prefix, but without affecting subscriptions zmq::xsub_t::xsend() – change to send rather than discard messages without 0 or 1 prefix, but without affecting subscriptions Update documentation
-
- 09 Nov, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 07 Nov, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 27 Oct, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 04 Jul, 2012 1 commit
-
-
Pieter Hintjens authored
-