- 17 Apr, 2020 1 commit
-
-
Doron Somech authored
When using ZMQ_HEARTBEAT one still needs to implement application-level heartbeat in order to know when to send a hello message. For example, with the majordomo protocol, the worker needs to send a READY message when connecting to a broker. If the connection to the broker drops, and the heartbeat recognizes it the worker won't know about it and won't send the READY msg. To solve that, the majordomo worker still has to implement heartbeat. With this new option, whenever the connection drops and reconnects the hello message will be sent, greatly simplify the majordomo protocol, as now READY and HEARTBEAT can be handled by zeromq.
-
- 27 Jan, 2020 3 commits
-
-
Simon Giesecke authored
Solution: add const/static
-
Simon Giesecke authored
Solution: add const
-
Simon Giesecke authored
Solution: use standard loop constructs and optimize some loops
-
- 26 Jan, 2020 1 commit
-
-
Simon Giesecke authored
Solution: fix handling of _starting and _terminate flags Add tests for this situation. Clarify documentation of zmq_ctx_shutdown and zmq_socket. Fixes #3792
-
- 25 Dec, 2019 1 commit
-
-
Simon Giesecke authored
Solution: add static
-
- 08 Dec, 2019 2 commits
-
-
Simon Giesecke authored
Solution: add const
-
Simon Giesecke authored
Solution: fix identifier names
-
- 02 Oct, 2019 1 commit
-
-
somdoron authored
Solution: support websocket with tls (wss)
-
- 11 Sep, 2019 1 commit
-
-
somdoron authored
Solution: allow to use external library (nss) for sha1 to avoid the conflict
-
- 27 Aug, 2019 1 commit
-
-
Francesco Montorsi authored
* Introduce DRAFT zmq_ctx_set_ext() and zmq_ctx_get_ext() methods. Change ZMQ_THREAD_NAME_PREFIX to allow for non-numeric thread name prefixes.
-
- 21 May, 2019 1 commit
-
-
Romain Moret authored
-
- 17 Feb, 2019 3 commits
-
-
Luca Boccassi authored
Solution: ifdef it
-
Luca Boccassi authored
Solution: use the thread class function rather than one of the pthread functions, and take into account the thread prefix context option
-
Kymeta Corp authored
Solution: 1. Use optional name parameter in thread_t::start for operating systems that have thread names. 2. Give start_thread() an optional name parameter for the thread's name. If this parameter is set, it will be appended to "0MQ:". If not set, "0MQ" will be used as the thread's name. 3. Give epoll the ability to name its thread. Then use this in io_thread and reaper to name them.
-
- 15 Jan, 2019 1 commit
-
-
Luca Boccassi authored
Solution: remove documents and tests for ZMQ_THREAD_PRIORITY getter. It never worked and can never work as it has the same value as a get-only option ZMQ_SOCKET_LIMIT. It cannot be changed without breaking ABI. Note that the setter works fine as ZMQ_SOCKET_LIMIT is get-only.
-
- 18 Nov, 2018 1 commit
-
-
Luca Boccassi authored
Solution: add one so that class-based bindings can easily use them
-
- 15 Aug, 2018 2 commits
-
-
Simon Giesecke authored
Solution: extract functionality into send_routing_id
-
Simon Giesecke authored
Solution: extract functionality into get_effective_conflate_option
-
- 09 Aug, 2018 1 commit
-
-
Simon Giesecke authored
-
- 07 Aug, 2018 1 commit
-
-
Simon Giesecke authored
-
- 28 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: use a std::vector instead
-
Simon Giesecke authored
Solution: introduced constant
-
- 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
-
- 26 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: configured clang-tidy check and applied fixes
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 18 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: replace by C++-style casts
-
- 13 May, 2018 1 commit
-
-
Luca Boccassi authored
Solution: do it explicitly to fix build on Solaris 10/11 with the Sun compiler
-
- 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.
-
- 22 Oct, 2017 1 commit
-
-
Simon Giesecke authored
Solution: use std::map::emplace instead, where available
-
- 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
-
- 19 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 07 Sep, 2017 1 commit
-
-
Doron Somech authored
-
- 06 Sep, 2017 1 commit
-
-
sigiesec authored
Solution: replace by "routing id"
-
- 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
-