- 16 Jun, 2016 1 commit
-
-
Douglas Cuthbertson authored
-
- 13 Jun, 2016 1 commit
-
-
Armin Burgmeier authored
On Windows, the written message does not seem to be guaranteed to be written to stderr, in particular when stderr is redirected to a file. I suppose this is because RaiseException terminates the process in a way that does not give the CRT a chance to flush stdio buffers (or if it does, there might be a problem when more than one CRT instance is linked into the program and they overwrite each other's exception handler). Either way, just make sure the assertion message ends up written to stderr to ease diagnostics.
-
- 11 Jun, 2016 2 commits
-
-
Michael Lutz authored
Solution: Provide poll() for Windows as well. This is a build option that defaults to off as the resulting binary will only run on Windows Vista or newer. This is not tested with alternative Winsock service providers like VMCI, but the documentation for WSAPoll does not mention limitations. On my local machine, throughput improves by ~10 % (20 simultaneous remote_thr workes to one local_thr, 10 byte messages), while latency improves by ~30 % (measured with remote/local_lat).
-
Michael Lutz authored
Solution: Always use fd_t when accessing the pollset.
-
- 09 Jun, 2016 2 commits
-
-
Luca Boccassi authored
Solution: use buffer address instead
-
Jose Luis Blanco-Claraco authored
(and probably other MSVC versions)
-
- 01 Jun, 2016 1 commit
-
-
Yann Diorcet authored
-
- 27 May, 2016 2 commits
-
-
Ilya Kulakov authored
It may even cause BSOD on Windows.
-
Adam Seering authored
On systems where getifaddrs() exists but isn't implemented, behave as if 'resolve_nic_name()' were entirely unsupported
-
- 20 May, 2016 1 commit
-
-
hitstergtd authored
Solution: Wrap to lte 80 chars and fix it.
-
- 19 May, 2016 2 commits
- 18 May, 2016 2 commits
-
-
evoskuil authored
-
Chris-P-Bacon authored
Since ZMQ_USE_SODIUM is nowhere defined i guess it's meant to be ZMQ_USE_LIBSODIUM?
-
- 16 May, 2016 8 commits
- 15 May, 2016 4 commits
-
-
Bitiquinho authored
-
Bitiquinho authored
-
Bitiquinho authored
-
Bitiquinho authored
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 13 May, 2016 1 commit
-
-
evoskuil authored
-
- 12 May, 2016 3 commits
-
-
hitstergtd authored
Solution: - Add checks for **poller_p_ to ensure that we do not segfault when either it or the value within it are NULL - Add tests for the above and increase error state coverage
-
hitstergtd authored
Solution: Mark them with LIBZMQ_UNUSED macro as per convention; although in future the appropriate pthread code should be updated to support thread scheduling priorities (for Mac OS X, et. al.)
-
evoskuil authored
-
- 11 May, 2016 1 commit
-
-
Erik Hugne authored
The TIPC protocol bindings in ZeroMQ defaults to a lookup domain of 1.0.0 to prevent 'closest first' search, and instead always do round robin if several sockets in the network or node have the same name published. In retrospect, this might have been a bad idea because it won't work on standalone configurations. We solve this by allowing an optional domain suffix to be provided in the address, and 0.0.0 should be used in that case, or if the TIPC address range in the cluster configuration is defined to some other value. Domain suffixes are only relevant for connecting addresses. Signed-off-by:
Erik Hugne <erik.hugne@gmail.com>
-
- 10 May, 2016 4 commits
-
-
hitstergtd authored
Solution: Mark it with LIBZMQ_UNUSED macro as per convention.
-
hitstergtd authored
Solution: Mark it with LIBZMQ_UNUSED as per our convention.
-
Doron Somech authored
-
Doron Somech authored
-
- 08 May, 2016 2 commits
-
-
hitstergtd authored
Solution: Indent it.
-
KIU Shueng Chuan authored
-
- 06 May, 2016 1 commit
-
-
Luca Boccassi authored
Solution: add an optional dependency on libunwind, and if present use it to print the backtrace when zmq_abort is called.
-
- 05 May, 2016 1 commit
-
-
Luca Boccassi authored
Solution: use socket object's mutex before the send_reap() call that might deallocate it
-