- 25 Apr, 2016 1 commit
-
-
hitstergtd authored
Solution: fix them
-
- 08 Mar, 2016 1 commit
-
-
Claudio Scordino authored
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 25 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 11 Sep, 2015 1 commit
-
-
Pieter Hintjens authored
We do not use 'get' for getters. Solution: rename to zmq_msg_routing_id () for public API.
-
- 05 Jun, 2015 1 commit
-
-
Richard Newton 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.
-
- 01 Feb, 2015 1 commit
-
-
somdoron authored
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 20 Jan, 2015 1 commit
-
-
Topher Brown authored
When pipe::write succeeds, it takes control of the message's data buffer. When it fails, it has not taken control. The caller should clean up the message appropriately (msg::close).
-
- 09 Jan, 2015 1 commit
-
-
Thomas Rodgers authored
Revert "linking fd to pipe identity via socket option" This reverts commit fe3e8c5c. Conflicts: include/zmq.h src/pipe.hpp src/session_base.cpp
-
- 16 Oct, 2014 1 commit
-
-
Sergey M․ authored
-
- 14 Aug, 2014 1 commit
-
-
Martin Hurton authored
-
- 12 Aug, 2014 1 commit
-
-
Martin Hurton authored
-
- 08 Aug, 2014 1 commit
-
-
kreuzberger authored
-
- 30 Apr, 2014 1 commit
-
-
Stoian Ivanov authored
-
- 12 Jan, 2014 1 commit
-
-
Martin Hurton authored
The get_credential () member function returns credential for the last peer we received message for. The idea is that this function is used to implement user-level API.
-
- 08 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 06 Jan, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 14 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 18 Aug, 2013 1 commit
-
-
Ian Barber authored
These were exposed to users, but have subsequently been removed as sockopts. They are currently only being used by ZAP, so I've moved it to a simpl function call (actually it's only used in one case even in that, so there may be a further simplification possible there).
-
- 17 Aug, 2013 1 commit
-
-
danielkr authored
ZMQ_CONFLATE option is passed to pipepair() which creates a usual ypipe_t or ypipe_conflate_t and plugs it into pipe_t under a common abstract base.
-
- 22 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 06 Jun, 2013 1 commit
-
-
Martin Hurton authored
-
- 28 May, 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.
-
- 28 Mar, 2012 1 commit
-
-
Martin Hurton authored
The check_write method does not use the passed message. The parameter was needed to implement the swap. As the swap is not supported anymore, it is safe to remove this parameter.
-
- 09 Nov, 2011 1 commit
-
-
AJ Lewis authored
Older versions of gcc have problems with in-line forward declarations when there's a naming conflict with a global symbol. Signed-off-by:
AJ Lewis <aj.lewis@quantum.com> Expand the original patch to all such forward declarations. 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 1 commit
-
-
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>
-
- 23 Jun, 2011 1 commit
-
-
Martin Sustrik authored
So far the requests in req/rep pattern were delivered to and processed by worker even though the original requester was dead. Thus, the worker processing replies with noone to deliver results to. This optimisation drops requests in two situations: 1. Queued inbound requests in XREP socket when peer disconnects. 2. Queued outbound requests in XREQ when socket is closed. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 22 Jun, 2011 1 commit
-
-
Martin Sustrik authored
Up to now the complexity of fair-queueing in XREP was O(n). Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 31 May, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 30 May, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 25 May, 2011 1 commit
-
-
Martin Sustrik authored
Till now the code was spread over mutliple locations. Additionally, the code was made more formally correct, with explicit pipe state machine etc. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 May, 2011 1 commit
-
-
Fabien Ninoles authored
Allow to have the same item part of two different arrays, as long as they are using different array identifier.
-
- 22 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, there was a pair of unidirectional pipes between a socket and a session (or an inproc peer). This resulted in complex problems with half-closed states and tracking which inpipe corresponds to which outpipe. This patch doesn't add any functionality in itself, but is essential for further work on features like subscription forwarding. 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>
-