Download The omniORBpy version 3 User's Guide

7.6. TRANSPORTS AND ENDPOINTS
57
The endpoint information to publish is determined by the endPointPublish
configuration parameter. It contains a comma-separated list of publish rules. The
rules are applied in turn to each of the configured endpoints; if a rule matches an
endpoint, it causes one or more endpoints to be published.
The following core rules are supported:
addr
ipv4
ipv6
name
hostname
fqdn
the first natural address of the endpoint
the first IPv4 address of a TCP or SSL endpoint
the first IPv6 address of a TCP or SSL endpoint
the first address that can be resolved to a name
the result of the gethostname() system call
the fully-qualified domain name
The core rules can be combined using the vertical bar operator to try several rules
in turn until one succeeds. e.g:
name|ipv6|ipv4
the name of the endpoint if it has one; failing that, its
first IPv6 address; failing that, its first IPv4 address.
Multiple rules can be combined using the comma operator to publish more than
one endpoint. e.g.
name,addr
the name of the endpoint (if it has one), followed by
its first address.
For endpoints with multiple addresses (e.g. TCP endpoints on multi-homed machines), the all() manipulator causes all addresses to be published. e.g.:
all(addr)
all(name)
all(name|addr)
all(name,addr)
all(name),
all(addr)
all addresses are published
all addresses that resolve to names are published
all addresses are published by name if they have one,
address otherwise.
all addresses are published by name (if they have
one), and by address.
first the names of all addresses are published, followed by all the addresses.
A specific endpoint can be published by giving its endpoint URI, even if the server
is not listening on that endpoint. e.g.:
giop:tcp:not.my.host:12345
giop:unix:/not/my/socket-file
If the host or port number for a TCP or SSL URI are missed out, they are filled