- 07 Mar, 2018 1 commit
-
-
Pontus.Skoeldstroem authored
* Tests for different TIPC address types and code cleanup * Adds tests for binding/connecting with different TIPC address types using Unity * Adds error checking for address type misuse
-
- 19 Feb, 2018 1 commit
-
-
Pontus Sköldström authored
ZeroMQ currently supports location independent addressing using TIPC Port Names with tipc://{type,instance}. This commits adds support for connecting and binding using TIPC Port Identity addresses. To connect using Port Identities the expected format is tipc://<Z.C.N:Ref>, e.g. "tipc://<1.2.3:123123>". To bind using TIPC Port Identities the expected format is "tipc://<*>".
-
- 02 Feb, 2018 1 commit
-
-
sigiesec authored
Solution: applied clang-format
-
- 10 Dec, 2016 1 commit
-
-
pavel.pimenov authored
-
- 11 May, 2016 1 commit
-
-
Erik Hugne authored
The TIPC protocol bindings in ZeroMQ defaults to a lookup domain of 1.0.0 to prevent 'closest first' search, and instead always do round robin if several sockets in the network or node have the same name published. In retrospect, this might have been a bad idea because it won't work on standalone configurations. We solve this by allowing an optional domain suffix to be provided in the address, and 0.0.0 should be used in that case, or if the TIPC address range in the cluster configuration is defined to some other value. Domain suffixes are only relevant for connecting addresses. Signed-off-by: Erik Hugne <erik.hugne@gmail.com>
-
- 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
-
- 02 Jan, 2014 2 commits
-
-
Pieter Hintjens authored
-
Pieter Hintjens authored
- corporate copyright statements sit in AUTHORS file
-
- 05 Nov, 2013 1 commit
-
-
Erik Hugne authored
By default, TIPC uses a closest first approach to find a publication that can satisfy your connection request. Any publication on the local node will automatically be chosen for all requests, even if you're trying to spread it out over multiple machines. We fix this by widening the default lookup scope. Signed-off-by: Erik Hugne <erik.hugne@ericsson.com>
-
- 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>
-