Man page - zmq_tipc(7)
Packages contas this manual
- zmq_connect(3)
- zmq_ipc(7)
- zmq_atomic_counter_new(3)
- zmq_vmci(7)
- zmq_null(7)
- zmq_atomic_counter_inc(3)
- zmq_ctx_set(3)
- zmq_disconnect(3)
- zmq_plain(7)
- zmq_socket(3)
- zmq_bind(3)
- zmq_z85_decode(3)
- zmq_curve_keypair(3)
- zmq_atomic_counter_destroy(3)
- zmq_msg_set_routing_id(3)
- zmq_tipc(7)
- zmq_poll(3)
- zmq_version(3)
- zmq_recv(3)
- zmq_socket_monitor_versioned(3)
- zmq_gssapi(7)
- zmq_msg_set(3)
- zmq_curve(7)
- zmq_inproc(7)
- zmq_socket_monitor(3)
- zmq_ctx_shutdown(3)
- zmq_atomic_counter_value(3)
- zmq_proxy_steerable(3)
- zmq_poller(3)
- zmq_getsockopt(3)
- zmq_setsockopt(3)
- zmq_msg_move(3)
- zmq_send_const(3)
- zmq_udp(7)
- zmq_proxy(3)
- zmq_errno(3)
- zmq_msg_size(3)
- zmq_msg_routing_id(3)
- zmq_msg_more(3)
- zmq_recvmsg(3)
- zmq_msg_recv(3)
- zmq_timers(3)
- zmq_z85_encode(3)
- zmq_atomic_counter_set(3)
- zmq_msg_init_size(3)
- zmq_ctx_term(3)
- zmq_msg_send(3)
- zmq_msg_data(3)
- zmq_has(3)
- zmq_msg_gets(3)
- zmq_msg_init_data(3)
- zmq_unbind(3)
- zmq_atomic_counter_dec(3)
- zmq_ppoll(3)
- zmq_ctx_new(3)
- zmq_msg_init_buffer(3)
- zmq_msg_close(3)
- zmq_send(3)
- zmq_msg_copy(3)
- zmq(7)
- zmq_ctx_get(3)
- zmq_pgm(7)
- zmq_msg_get(3)
- zmq_sendmsg(3)
- zmq_close(3)
- zmq_curve_public(3)
- zmq_connect_peer(3)
- zmq_tcp(7)
- zmq_strerror(3)
- zmq_msg_init(3)
apt-get install libzmq3-dev
Manual
| ZMQ_TIPC(7) | 0MQ Manual | ZMQ_TIPC(7) |
NAME
zmq_tipc - 0MQ unicast transport using TIPC
SYNOPSIS
TIPC is a cluster IPC protocol with a location transparent addressing scheme.
ADDRESSING
A 0MQ endpoint is a string consisting of a transport:// followed by an address. The transport specifies the underlying protocol to use. The address specifies the transport-specific address to connect to.
For the TIPC transport, the transport is tipc, and the meaning of the address part is defined below.
Assigning a port name to a socket
When assigning a port name to a socket using zmq_bind() with the tipc transport, the endpoint is defined in the form: {type, lower, upper}
Publishing the same service with overlapping lower/upper ID’s will cause connection requests to be distributed over these in a round-robin manner.
Connecting a socket
When connecting a socket to a peer address using zmq_connect() with the tipc transport, the endpoint shall be interpreted as a service ID, followed by a comma and the instance ID.
The instance ID must be within the lower/upper range of a published port name for the endpoint to be valid.
EXAMPLES
Assigning a local address to a socket.
// Publish TIPC service ID 5555
rc = zmq_bind(socket, "tipc://{5555,0,0}");
assert (rc == 0);
// Publish TIPC service ID 5555 with a service range of 0-100
rc = zmq_bind(socket, "tipc://{5555,0,100}");
assert (rc == 0);
Connecting a socket.
// Connect to service 5555 instance id 50
rc = zmq_connect(socket, "tipc://{5555,50}");
assert (rc == 0);
SEE ALSO
zmq_bind(3) zmq_connect(3) zmq_tcp(7) zmq_pgm(7) zmq_ipc(7) zmq_inproc(7) zmq_vmci(7) zmq(7)
AUTHORS
This page was written by the 0MQ community. To make a change please read the 0MQ Contribution Policy at http://www.zeromq.org/docs:contributing.
| 10/29/2024 | 0MQ 4.3.5 |