Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in / Register
Toggle navigation
L
libzmq
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Packages
Packages
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
submodule
libzmq
Commits
bbbccebb
Commit
bbbccebb
authored
Nov 05, 2013
by
Erik Hugne
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
zmq: add TIPC manpage
Signed-off-by:
Erik Hugne
<
erik.hugne@ericsson.com
>
parent
0d5ffd5a
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
83 additions
and
1 deletion
+83
-1
Makefile.am
doc/Makefile.am
+1
-1
zmq_tipc.txt
doc/zmq_tipc.txt
+82
-0
No files found.
doc/Makefile.am
View file @
bbbccebb
...
...
@@ -12,7 +12,7 @@ MAN3 = zmq_bind.3 zmq_unbind.3 zmq_connect.3 zmq_disconnect.3 zmq_close.3 \
zmq_z85_encode.3 zmq_z85_decode.3 zmq_curve_keypair.3
MAN7
=
zmq.7 zmq_tcp.7 zmq_pgm.7 zmq_epgm.7 zmq_inproc.7 zmq_ipc.7
\
zmq_null.7 zmq_plain.7 zmq_curve.7
zmq_null.7 zmq_plain.7 zmq_curve.7
zmq_tipc.7
MAN_DOC
=
$(MAN1)
$(MAN3)
$(MAN7)
...
...
doc/zmq_tipc.txt
0 → 100644
View file @
bbbccebb
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}
* Type is the numerical (u32) ID of your service.
* Lower and Upper specify a range for your service.
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
--------
linkzmq:zmq_bind[3]
linkzmq:zmq_connect[3]
linkzmq:zmq_tcp[7]
linkzmq:zmq_pgm[7]
linkzmq:zmq_ipc[7]
linkzmq:zmq_inproc[7]
linkzmq: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>.
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment