- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Problem: inconsistent naming style for private data members, conflicts with naming of local variables and member functions Solution: apply and check _lower_case naming style for private data members
-
- 22 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: removed
-
- 09 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: Add IPv6 support
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 15 Nov, 2016 1 commit
-
-
Caleb Epstein authored
Solution: Fix typo of 'mutlicast' -> 'multicast'
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 29 Apr, 2016 1 commit
-
-
somdoron authored
-
- 07 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
Solution: fix these.
-
- 30 Jan, 2016 1 commit
-
-
Joe Eli McIlvain authored
Resolves #1739.
-
- 29 Jan, 2016 1 commit
-
-
somdoron authored
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 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
-
- 01 Jul, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 Jan, 2014 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
- corporate copyright statements sit in AUTHORS file
-
- 01 Nov, 2013 2 commits
-
-
Erik Hugne authored
As TIPC transport for 0MQ will only work on post 3.8 Linux kernels where nonblocking connect was added, we add AC_RUN test to check for this functionality. Should the test fail, tipc is excluded from build/test. Signed-off-by:
Erik Hugne <erik.hugne@ericsson.com>
-
Erik Hugne authored
A ZeroMQ application can opt for TIPC based sockets using the TIPC port name format: zmq_bind(sb, "tipc://{type,lower,upper}"); zmq_connect(sc, "tipc://{type,inst}"); 'type' is the service ID, and 'lower/upper' can be used for service partitioning or basic load balancing. ZeroMQ TIPC transport requires a kernel >= 3.8 (nonblocking connect support for TIPC). Signed-off-by:
Erik Hugne <erik.hugne@ericsson.com>
-
- 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.
-
- 18 Apr, 2012 1 commit
-
-
Sergey KHripchenko authored
-
- 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>
-
- 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>
-
- 18 Aug, 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>
-
- 28 May, 2011 1 commit
-
-
Martin Sustrik authored
This patch will prevent duplicate matching in devices in the future. Instead of matching in both XPUB and XSUB, it'll happen only in XPUB. Receiver endpoint will still filter messages via SUB socket. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 23 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, the pipe termination code was spread among socket type classes, fair queuer, load balancer, etc. This patch moves all the associated logic to a single place. 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>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 13 Jan, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 07 Jan, 2011 1 commit
-
-
Martin Sustrik authored
The ability was inherited from XSUB socket. Now it's properly disabled. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 05 Dec, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 04 Dec, 2010 1 commit
-
-
Martin Sustrik authored
These are just placeholders. At the moment XPUB behaves th same as PUB and XSUB as SUB. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 05 Nov, 2010 1 commit
-
-
Martin Sustrik authored
Threads were so far identified by integers called 'slots'. This patch renames them to more comprehensible 'tid's (thread IDs). Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 30 Oct, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 16 Oct, 2010 1 commit
-
-
Martin Sustrik authored
1. ZMQ_LINGER option can be set/get 2. options are part of own_t base class rather than being declared separately by individual objects 3. Linger option is propagated with "term" command so that the newest value of it is used rather than the stored old one. 4. Session sets the linger timer if needed and terminates as soon as it expires. 5. Corresponding documentation updated. Signed-off-by:
Martin Sustrik <sustrik@250bpm.com>
-
- 18 Sep, 2010 1 commit
-
-
Martin Sustrik authored
-
- 28 Aug, 2010 1 commit
-
-
Martin Sustrik authored
-
- 25 Aug, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
Sockets may now be migrated between OS threads; sockets may not be used by more than one thread at any time. To migrate a socket to another thread the caller must ensure that a full memory barrier is called before using the socket from the target thread. The new zmq_close() semantics implement the behaviour discussed at: http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html Specifically, zmq_close() is now deterministic and while it still returns immediately, it does not discard any data that may still be queued for sending. Further, zmq_term() will now block until all outstanding data has been sent. TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or an equivalent mechanism (possibly a configurable timeout to zmq_term()) needs to be implemented.
-