- 05 Mar, 2018 1 commit
-
-
Stefan Kaes authored
The zero copy decoding strategy implemented for 4.2.0 can lead to a large increase of main memory usage in some cases (I have seen one program go up to 40G from 10G after upgrading from 4.1.4). This commit adds a new option to contexts, called ZMQ_ZERO_COPY_RECV, which allows one to switch to the old decoding strategy.
-
- 11 Feb, 2018 1 commit
-
-
Simon Giesecke authored
Solution: extract thread_ctx_t from ctx_t
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 31 Jan, 2018 1 commit
-
-
sigiesec authored
Solution: signal error to caller, and apply appropriate cleanup
-
- 25 Oct, 2017 1 commit
-
-
f18m authored
Change ZMQ_THREAD_AFFINITY to ZMQ_THREAD_AFFINITY_CPU_ADD/ZMQ_THREAD_AFFINITY_CPU_REMOVE. Avoid prefix thread names when no prefix was set.
-
- 17 Oct, 2017 1 commit
-
-
f18m authored
* Add ZMQ_THREAD_NAME_PREFIX ctx option
-
- 16 Oct, 2017 1 commit
-
-
f18m authored
* Background thread scheduling - add ZMQ_THREAD_AFFINITY ctx option; set all thread scheduling options from the context of the secondary thread instead of using the main process thread context! - change ZMQ_THREAD_PRIORITY to support setting NICE of the background thread when using SCHED_OTHER
-
- 28 Jul, 2017 1 commit
-
-
Luca Boccassi authored
Solution: add a crypto [de-]initialiser, refcounted and serialised through critical sections. This is necessary as utility APIs such as zmq_curve_keypair also call into the sodium/tweetnacl libraries and need the initialisation outside of the zmq context. Also the libsodium documentation explicitly says that sodium_init must not be called concurrently from multiple threads, which could have happened until now. Also the randombytes_close function does not appear to be thread safe either. This change guarantees that the library is initialised only once at any given time across the whole program. Fixes #2632
-
- 29 Mar, 2016 1 commit
-
-
Nikolay Edigaryev authored
libsodium calls abort() when /dev/urandom can't be found even if one creates ZeroMQ context before calling chroot()[1]. This happens because crypto gets initialized on handshake, and at that moment the process is already chroot'ed. Solution: initialize cryptographic libraries in ctx randombytes_close() is already there in the destructor. [1] https://download.libsodium.org/doc/usage/index.html
-
- 09 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
And I'm on a reasonably sized laptop. I think allocating INT_MAX memory is dangerous in a test case. Solution: expose this as a context option. I've used ZMQ_MAX_MSGSZ and documented it and implemented the API. However I don't know how to get the parent context for a socket, so the code in zmq.cpp is still unfinished.
-
- 01 Feb, 2016 3 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
-
Constantin Rack authored
Solution: replace with `zmq_ctx_term` Also fix whitespace (tabs instead of spaces)
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 08 Dec, 2015 1 commit
-
-
Ilya Kulakov authored
VMCI transport allows fast communication between the Host and a virtual machine, between virtual machines on the same host, and within a virtual machine (like IPC). It requires VMware to be installed on the host and Guest Additions to be installed on a guest.
-
- 20 Aug, 2015 1 commit
-
-
Joe Eli McIlvain authored
Solution: Convert to spaces and remove trailing whitespace in these files.
-
- 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.
-
- 12 Feb, 2015 1 commit
-
-
somdoron authored
-
- 22 Jan, 2015 1 commit
-
-
Pieter Hintjens authored
Solution: update for 2015 Fixes #1320
-
- 17 Nov, 2014 1 commit
-
-
Pieter Hintjens authored
Solution: set defaults back to infinity, and add new context option, ZMQ_BLOCKY that the user can set to false to get a less surprising behavior on context termination. Eg. zmq_ctx_set (ctx, ZMQ_BLOCKY, false);
-
- 09 Jul, 2014 1 commit
-
-
Martin Hurton authored
-
- 02 Jul, 2014 1 commit
-
-
Joel Lauener authored
environment variables.
-
- 23 May, 2014 1 commit
-
-
Martin Hurton authored
-
- 21 May, 2014 1 commit
-
-
Martin Hurton authored
- limit visibility of pending_connection_t - add const qualifiers
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 07 Oct, 2013 1 commit
-
-
- 14 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 12 Sep, 2013 3 commits
-
-
Richard Newton authored
-
Richard Newton authored
-
Richard Newton authored
-
- 10 Sep, 2013 1 commit
-
-
Richard Newton authored
-
- 01 Sep, 2013 1 commit
-
-
Matt Connolly authored
Terminate context in a child process of fork() to replace file descriptors to not interfere with parent process's context
-
- 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.
-
- 31 Jan, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 21 Sep, 2012 1 commit
-
-
Lourens Naudé authored
Significantly reworked the monitoring infrastructure with a more granular per socket API and to play well with monitoring endpoints in application threads
-
- 24 Aug, 2012 1 commit
-
-
Arthur O'Dwyer authored
There are three versions of monitor_event(), all taking variadic arguments. The original code just has the first one creating a va_list and passing that va_list variadically to the second one... which creates a new va_list and passes it variadically to the third one... and of course everything blows up when we try to pull a non-va_list argument off the stack. The correct approach matches the C standard library's use of printf/vprintf, scanf/vscanf, and so on. Once you make a va_list, you must pass it only to functions which expect a va_list parameter.
-
- 21 May, 2012 2 commits
-
-
Lourens Naudé authored
-
Lourens Naudé authored
-
- 22 Mar, 2012 2 commits
-
-
Pieter Hintjens authored
-
Martin Hurton authored
* corrects whitespace errors * fixes spelling errors in comments * prefers #ifdef to #if defined
-