- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 02 Jun, 2015 1 commit
-
-
Pieter Hintjens authored
Of course people still "can" distributed the sources under the LGPLv3. However we provide COPYING.LESSER with additional grants. Solution: specify these grants in the header of each source file.
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 12 Mar, 2014 1 commit
-
-
Mark Barbisan authored
-
- 08 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 20 Sep, 2013 1 commit
-
-
Pieter Hintjens authored
* ZMQ_REQ_STRICT was negative option (default 1) which goes against the standard, where defaults are zero. I renamed this to ZMQ_REQ_RELAXED. * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE which seems more explicit.
-
- 24 Aug, 2013 1 commit
-
-
Evan Burkitt authored
Added some missing (but existing in branch) files to libzmq11 project needed to compile as static library by VS2012 (at least), and fixed some warnings. One warning remains in raw_decoder.cpp, which I'm leaving for now because I'm not sure how project owners would like to fix it.
-
- 03 Aug, 2013 1 commit
-
-
Christian Kamm authored
It defaults to enabled. Switch it off to be able to send a new message before the previous reply has been received.
-
- 29 Jul, 2013 1 commit
-
-
Christian Kamm authored
* Fixes a terminate() call on a dangling pointer in the SEND_RESETS case. * Fixes recv_reply_pipe() never receiving a message once the pipe it is waiting on is terminated.
-
- 28 Jul, 2013 1 commit
-
-
Christian Kamm authored
This allows making a new request on a REQ socket by sending a new message. Without the option set, calling send() after the first message is done will continue to return an EFSM error. It's useful for when a REQ is not getting a response. Previously that meant creating a new socket or switching to DEALER.
-
- 26 Jul, 2013 1 commit
-
-
Christian Kamm authored
* Documentation: The default behavior of REQ sockets is to rely on the ordering of messages to match requests and responses and that is usually sufficient. When this option is set to 1, the REQ socket will prefix outgoing messages with an extra frame containing a request id. That means the full message is (request id, 0, user frames...). The REQ socket will discard all incoming messages that don't begin with these two frames. * Behavior change: When a REQ socket gets an invalid reply, it used to discard the message and return EAGAIN. REQ sockets still discard invalid messages, but keep looking at the next one automatically until a good one is found or there are no more messages. * Add test_req_request_ids.
-
- 14 Jul, 2013 1 commit
-
-
Christian Kamm authored
* Add lb_t::sendpipe() that returns the pipe that was used for sending, similar to fq_t::recvpipe(). * Add forwarder functions to dealer_t to access these two. * Add logic to req_t to ignore replies on pipes that are not the one where the request was sent. * Enable test in test_spec_req.
-
- 29 Jun, 2013 2 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
- 11 Apr, 2013 1 commit
-
-
Martin Hurton authored
-
- 12 Mar, 2013 1 commit
-
-
Pieter Hintjens authored
Copyrights had become ads for Sustrik's corporate sponsors, going against the original agreement to share copyrights with the community (that agreement was: one line stating iMatix copyright + one reference to AUTHORS file). The proliferation of corporate ads is also unfair to the many individual authors. I've removed ALL corporate title from the source files so the copyright statements can now be centralized in AUTHORS and source files can be properly updated on an annual basis.
-
- 09 Nov, 2012 3 commits
-
-
Martin Hurton authored
-
Martin Hurton authored
-
Martin Hurton authored
-
- 02 Sep, 2012 1 commit
-
-
Martin Hurton authored
This patch introduces i_msg_sink and i_msg_source interfaces. This allows us to make message encoder and decoder more general.
-
- 29 May, 2012 1 commit
-
-
Martin Hurton authored
The patch extends the internal session's API with the reset method. This method is used to reset a session's state so that it can handle a new connection.
-
- 22 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
-
- 20 Mar, 2012 1 commit
-
-
Pieter Hintjens authored
* Implemented new ctx API (_new, _destroy, _get, _set) * Removed 'typesafe' macros from zmq.h * Added support for MAX_SOCKETS (was tied into change for #337) * Created new man pages
-
- 16 Feb, 2012 1 commit
-
-
Staffan Gimåker authored
This allows us to actually report an error to the caller on resolve failure, rather than asserting later on in the io thread. Signed-off-by:
Staffan Gimåker <staffan@spotify.com>
-
- 08 Nov, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 04 Nov, 2011 1 commit
-
-
Martin Sustrik authored
However, the "durable socket" behaviour wasn't re-added. Identities are used solely for routing in REQ/REP pattern. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 01 Nov, 2011 2 commits
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 31 Oct, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 29 Oct, 2011 1 commit
-
-
Perry Kundert authored
When zmq::req_t::xrecv detects that a response has no request ID label, or the ID is the wrong size, it would return an EAGAIN, but would not discard the remainder of the message. This could allow the remainder of the message to incorrectly "leak" into a future response, if it is crafted to look like a reply with a valid response ID. Discard all remaining message blocks, if the ID is invalid in any way.
-
- 16 Sep, 2011 1 commit
-
-
Martin Sustrik authored
This patch adds support for checking messages as they arrive (as opposed to when they are recv'd by the user) and drop the connection if they are malformed. It also uses this new feature to check for validity of inbound messages in REQ socket. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 15 Sep, 2011 1 commit
-
-
Martin Sustrik authored
This is a preliminary patch allowing for socket-type-specific functionality in the I/O thread. For example, message format can be checked asynchronously and misbehaved connections dropped straight away. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 13 Sep, 2011 1 commit
-
-
Mikko Koppanen authored
Signed-off-by:
Mikko Koppanen <mkoppanen@php.net> Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 15 Jul, 2011 1 commit
-
-
Martin Sustrik authored
This patch simplifies the whole codebase significantly, including dropping depedency on libuuid. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 22 Jun, 2011 1 commit
-
-
Martin Sustrik authored
This patch introduces two changes: 1. 32-bit ID is used to identify the peer instead of UUID 2. REQ socket seeds the label stack with unique 32-bit request ID It also drops any replies with non-matching request ID Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 20 Jun, 2011 1 commit
-
-
Martin Sustrik authored
So far there was no distinction between message parts used by 0MQ and message parts used by user. Now, the message parts used by 0MQ are marked as 'LABEL'. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 21 Apr, 2011 1 commit
-
-
Martin Sustrik authored
This patch addresses serveral issues: 1. It gathers message related functionality scattered over whole codebase into a single class. 2. It makes zmq_msg_t an opaque datatype. Internals of the class don't pollute zmq.h header file. 3. zmq_msg_t size decreases from 48 to 32 bytes. That saves ~33% of memory in scenarios with large amount of small messages. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 19 Apr, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-