- 31 Aug, 2018 2 commits
-
-
Luca Boccassi authored
Solution: fix them
-
Byron Mallett authored
* Added SO_REUSEPORT socket option for UDP multicast recv ports
-
- 09 Aug, 2018 1 commit
-
-
Simon Giesecke authored
Solution: prevent access to data if the object was deleted
-
- 31 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: add TODO comment regarding handling of the result
-
- 28 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: use char* from the beginning
-
- 27 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: replace by static_cast/reinterpret_cast
-
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 1 commit
-
-
Simon Giesecke authored
Solution: define and apply parameter naming style: lower_case_
-
- 22 May, 2018 2 commits
-
-
Simon Giesecke authored
Solution: add const
-
Simon Giesecke authored
Solution: removed
-
- 18 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: replace by C++-style casts
-
- 16 May, 2018 1 commit
-
-
Antony Searle authored
-
- 15 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: fix handling of sockaddr in recvfrom
-
- 14 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: fix type specification
-
- 13 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: if a binding interface is provided in the sender URL we pass it to IP[V6]_MULTICAST_IF setsockopt
-
- 10 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: add a new ZMQ_MULTICAST_LOOP option for UDP sockets.
-
- 09 May, 2018 1 commit
-
-
Lionel Flandrin authored
Solution: Add IPv6 support
-
- 20 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
-
- 19 Mar, 2018 1 commit
-
-
Pontus Sköldström authored
-
- 10 Mar, 2018 1 commit
-
-
Manuel Segura authored
* Problem: Still need to port over more files to VxWorks 6.x Solution: Port more files to VxWorks 6.x * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes) Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x. Solution: Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 08 Aug, 2017 1 commit
-
-
Simon Giesecke authored
* Problem: missing test for status code 300, inadequate assertion for status code 500 Solution: add test, change assertion (currently test fails) * Problem: gcc compiler error deprecated conversion from string constant Solution: declare variable as const * Problem: in case of ZAP handler returning a status code other than 200, no appropriate event is emitted Solution: immediately emit event after receiving reply from ZAP handler * Problem: endpoint address is not included in zap-reply monitor event Solution: added functions to retrieve endpoint address in zmq::i_engine and zmq::session_base_t removed unused code block in zmq::stream_engine_t::next_handshake_command * Problem: wrong formatting Solution: fix formatting * Problem: test fails because of EPIPE Solution: add EPIPE/ECONNRESET/ECONNAGAIN handling for more test cases
-
- 31 Jul, 2017 2 commits
-
-
Luca Boccassi authored
Solution: apply the option outside of the send/recv_enabled blocks so that it is used for all types of UDP sockets
-
Brian Russell authored
Linux now supports Virtual Routing and Forwarding (VRF) as per: https://www.kernel.org/doc/Documentation/networking/vrf.txt In order for an application to bind or connect to a socket with an address in a VRF, they need to first bind the socket to the VRF device: setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1); Note "dev" is the VRF device, eg. VRF "blue", rather than an interface enslaved to the VRF. Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device. In general, if a socket is bound to a device, eg. an interface, only packets received from that particular device are processed by the socket. If device is a VRF device, then subsequent binds/connects to that socket use addresses in the VRF routing table.
-
- 01 Jun, 2016 1 commit
-
-
Yann Diorcet authored
-
- 18 May, 2016 1 commit
-
-
evoskuil authored
-
- 16 May, 2016 3 commits
-
-
somdoron authored
-
Doron Somech authored
-
somdoron authored
-
- 15 May, 2016 1 commit
-
-
Bitiquinho authored
-
- 14 May, 2016 1 commit
-
-
evoskuil authored
-
- 21 Feb, 2016 5 commits
-
-
Luca Boccassi authored
Solution: use NULL instead to avoid build failure with older compilers.
-
Luca Boccassi authored
Solution: initialize to -1, since fd is a file descriptor (int).
-
Luca Boccassi authored
Solution: initialize class variable in the same order as they are defined.
-
Luca Boccassi authored
Solution: fix it
-
Osiris authored
Solution: The Coverity Static Code Analyzer was used on libzmq code and found many issues with uninitialized member variables, some redefinition of variables hidding previous instances of same variable name and a couple of functions where return values were not checked, even though all other occurrences were checked (e.g. init_size() return).
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 07 Feb, 2016 1 commit
-
-
Pieter Hintjens authored
Solution: fix these.
-
- 01 Feb, 2016 1 commit
-
-
Usama Mehboob authored
-
- 30 Jan, 2016 1 commit
-
-
somdoron authored
-