- 05 Apr, 2019 1 commit
-
-
Serhio authored
* Some explicit endpoint type changes to support GCC 5 * ../RELICENSE/SergheiNovac.md
-
- 02 Feb, 2019 1 commit
-
-
Simon Giesecke authored
Problem: get_socket_address and get_socket_name not available throughout libzmq and restricted to local address Solution: move to address.hpp/.cpp and generalize
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 10 Dec, 2016 1 commit
-
-
pavel.pimenov authored
-
- 03 Feb, 2016 1 commit
-
-
Ilya Kulakov authored
select was improved to support multiple service providers on Windows. it should be slightly faster because of optimized iteration over selected sockets.
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 22 Jan, 2016 1 commit
-
-
Ilya Kulakov authored
-
- 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.
-
- 06 Sep, 2015 1 commit
-
-
Constantin Rack authored
-
- 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
-
- 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>
-
- 15 Jun, 2013 1 commit
-
-
xinchuan authored
-
- 17 May, 2013 1 commit
-
-
Pieter Hintjens authored
- we need to switch to PLAIN according to options.mechanism - we need to catch case when both peers are as-server (or neither is) - and to use username/password from options, for client
-
- 14 May, 2013 1 commit
-
-
Martin Hurton authored
This implements protocol handshake. We still need to design and implement 1) API changes so a user can set username and password, and 2) a mechanism for engine to authenticate users.
-
- 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.
-
- 22 Jan, 2013 1 commit
-
-
Charles McGarvey authored
This accomplishes the same thing as 2e2ef7fd in a potentially cleaner way.
-
- 21 Jan, 2013 1 commit
-
-
Charles McGarvey authored
-
- 17 Nov, 2012 1 commit
-
-
Lourens Naudé authored
Copy monitor specific event endpoints to event messages as the engine etc. can be released at anytime
-
- 30 Sep, 2012 1 commit
-
-
Michel Pelletier authored
Handle insufficient resources on accept() decently If accept() call fails due to insuffient OS resources the new connection is rejected.
-
- 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
-
- 04 Aug, 2012 1 commit
-
-
Lourens Naudé authored
-
- 13 Jul, 2012 1 commit
-
-
Martin Hurton authored
When closing an ipc listener, the library may try to unlink the associated file. When this fails, the underlying socket is not marked as retired and this triggers assertion failure. Fixes issue #397
-
- 11 Jul, 2012 1 commit
-
-
Martin Hurton authored
This also fixes a bug in tcp_connecter and tcp_listener, which generated the event not when they failed to close the socket but when the succeed to close it.
-
- 13 Jun, 2012 1 commit
-
-
Martin Hurton authored
-
- 12 Jun, 2012 2 commits
-
-
Ian Barber authored
This reverts commit dde69fb9.
-
Ian Barber authored
This reverts commit 7b105865, reversing changes made to 33459029.
-
- 11 Jun, 2012 1 commit
-
-
Martin Hurton authored
Once the object has been terminated, it is unsafe for this object to refer to its parent. The bug was responsible for occasional test_shutdown_stress failures.
-
- 05 Jun, 2012 1 commit
-
-
AJ Lewis authored
The socket length variable for getsockname and accept must be an (int *) instead of a (socklen_t *) on HPUX. Signed-off-by:
AJ Lewis <aj.lewis@quantum.com>
-
- 04 May, 2012 1 commit
-
-
Lourens Naudé authored
-
- 21 Apr, 2012 1 commit
-
-
Sergey KHripchenko authored
1. when we call zmq_bind()/zmq_connect() to create endpoint we send ourselfs(through launch_child()) command to process_own(endpoint) (and add it to own_t::owned) in the application thread we could call zmq_unbind() / zmq_disconnect() _BEFORE_ we run process_own() in ZMQ thread and in this situation we will be unable to find it in own_t::owned. in other words own_t::owned.find(endpoint) will not be deleted but it will be deleted from socket_base_t::endpoints. 2. when you zmq_unbind() the lisnening TCP/IPC socket was terminated only in destructor... so the whole ZMQ_LINGER time listening TCP/IPC socket was able to accept() new connections but unable to handle them. this all geting even worse since unfortunately zmq has a bug and '*_listener_t' object not terminated untill the socket's zmq_close(). AT LEAST FOR PUSH SOCKETS. Everything is ok for SUB sockets. Easy to reproduce without my fix: zmq_socket(PUSH) zmq_bind(tcp); // connect to it from PULL socket zmq_unbind(tcp); sleep(forever) // netstat -anp | grep 'tcp listening socket' With my fix you could see that after zmq_unbind(tcp) all previously connected tcp sessions will not be finished untill the zmq_close(socket) regardless of ZMQ_LINGER value. (*_listener_t terminates all owned session_base_t(connect=false) and they call pipe_t::terminate() which in turn should call session_base_t::terminated() but this never happens)
-
- 18 Apr, 2012 1 commit
-
-
Sergey KHripchenko authored
-
- 01 Mar, 2012 1 commit
-
-
Rob Gagnon authored
-
- 18 Feb, 2012 1 commit
-
-
Mikko Koppanen authored
-
- 17 Feb, 2012 1 commit
-
-
Mikko Koppanen 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>
-
- 14 Feb, 2012 1 commit
-
-
Ian Barber authored
-