- 06 Feb, 2019 3 commits
-
-
Simon Giesecke authored
Solution: use addrlen to determine the length
-
Simon Giesecke authored
Solution: rename data member
-
Simon Giesecke authored
Solution: use memcpy instead
-
- 10 Aug, 2018 1 commit
-
-
Simon Giesecke authored
-
- 30 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: change to comply with naming conventions
-
- 27 May, 2018 1 commit
-
-
Simon Giesecke authored
Solution: replace by static_cast/reinterpret_cast
-
- 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
-
- 18 Feb, 2016 1 commit
-
-
Osiris authored
Solution: Phase I - make precompiled.hpp be first file included in every source file
-
- 28 Jan, 2016 1 commit
-
-
Constantin Rack authored
Solution: update to 2016
-
- 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
-
- 01 Jul, 2014 1 commit
-
-
Martin Hurton authored
-
- 05 May, 2014 1 commit
-
-
Franco Fichtner authored
Using 'ipc://@abstract-socket' on non-Linux platforms yields inconsistent behaviour. Abstract sockets don't exist, so the literal file is created. The test previously failed, but for a different reason: this is not the directory you are looking for. Now, zmq_bind() will fail for the right reason: the socket can't be created. Put the XFAIL back.
-
- 02 Jan, 2014 1 commit
-
-
Pieter Hintjens authored
-
- 20 Dec, 2013 1 commit
-
-
Pieter Hintjens authored
-
- 07 Oct, 2013 1 commit
-
-
Brandon Carpenter authored
Abstract socket pathnames must have a NULL character in the first position, but the second character must also be checked to differentiate an abstract name from the empty string. The address length must also indicate the length of the pathname because the kernel uses the entire address as the name, including NULL characters. ZMQ uses NULL-terminated strings for the address, so the abstract address length is the length of the string following the initial NULL byte plus 3; two bytes for the address family and one for the initial NULL character.
-
- 04 Oct, 2013 1 commit
-
-
Brandon Carpenter authored
Converts an initial strudel or "at sign" (@) in the Unix socket path to a NULL character ('\0') indicating that the socket uses the abstract namespace instead of the filesystem namespace. For instance, binding a socket to 'ipc://@/tmp/tester' will not create a file associated with the socket whereas binding to 'ipc:///tmp/tester' will create the file /tmp/tester. See issue 567 for more information.
-
- 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.
-
- 18 Apr, 2012 1 commit
-
-
Sergey KHripchenko 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>
-
- 01 Nov, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 31 Oct, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 18 Aug, 2011 2 commits
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 15 Jul, 2011 1 commit
-
-
Martin Sustrik authored
This patch simplifies the whole codebase significantly, including dropping depedency on libuuid. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 23 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, the pipe termination code was spread among socket type classes, fair queuer, load balancer, etc. This patch moves all the associated logic to a single place. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 22 May, 2011 1 commit
-
-
Martin Sustrik authored
So far, there was a pair of unidirectional pipes between a socket and a session (or an inproc peer). This resulted in complex problems with half-closed states and tracking which inpipe corresponds to which outpipe. This patch doesn't add any functionality in itself, but is essential for further work on features like subscription forwarding. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 21 Apr, 2011 1 commit
-
-
Martin Sustrik authored
This patch addresses serveral issues: 1. It gathers message related functionality scattered over whole codebase into a single class. 2. It makes zmq_msg_t an opaque datatype. Internals of the class don't pollute zmq.h header file. 3. zmq_msg_t size decreases from 48 to 32 bytes. That saves ~33% of memory in scenarios with large amount of small messages. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 02 Mar, 2011 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 05 Nov, 2010 1 commit
-
-
Martin Sustrik authored
Threads were so far identified by integers called 'slots'. This patch renames them to more comprehensible 'tid's (thread IDs). Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 30 Oct, 2010 1 commit
-
-
Martin Sustrik authored
Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 16 Oct, 2010 1 commit
-
-
Martin Sustrik authored
1. ZMQ_LINGER option can be set/get 2. options are part of own_t base class rather than being declared separately by individual objects 3. Linger option is propagated with "term" command so that the newest value of it is used rather than the stored old one. 4. Session sets the linger timer if needed and terminates as soon as it expires. 5. Corresponding documentation updated. Signed-off-by: Martin Sustrik <sustrik@250bpm.com>
-
- 28 Sep, 2010 1 commit
-
-
Gonzalo Diethelm authored
-
- 18 Sep, 2010 1 commit
-
-
Martin Sustrik authored
-
- 25 Aug, 2010 2 commits
-
-
Martin Sustrik authored
-
Martin Sustrik authored
Sockets may now be migrated between OS threads; sockets may not be used by more than one thread at any time. To migrate a socket to another thread the caller must ensure that a full memory barrier is called before using the socket from the target thread. The new zmq_close() semantics implement the behaviour discussed at: http://lists.zeromq.org/pipermail/zeromq-dev/2010-July/004244.html Specifically, zmq_close() is now deterministic and while it still returns immediately, it does not discard any data that may still be queued for sending. Further, zmq_term() will now block until all outstanding data has been sent. TODO: Many bugs have been introduced, needs testing. Further, SO_LINGER or an equivalent mechanism (possibly a configurable timeout to zmq_term()) needs to be implemented.
-
- 04 Aug, 2010 1 commit
-
-
Pieter Hintjens authored
definitions as aliases, to be removed in release 3.0. Also renamed the source files implementing these two socket types. This change does not break existing applications nor bindings, but allows us to fix the documentation and user guide now, rather than keeping the old (confusing) names.
-
- 13 Mar, 2010 1 commit
-
-
Martin Sustrik authored
-
- 12 Mar, 2010 1 commit
-
-
Martin Hurton authored
This commit introduces the necessary changes necessary for implementing flow control. None of the socket types implements the flow control yet. The code will crash when the flow control is enabled and the thw lwm is reached. The following commits will add flow-control support for individual socket types.
-