summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorschmidt <douglascraigschmidt@users.noreply.github.com>2007-06-04 11:40:11 +0000
committerschmidt <douglascraigschmidt@users.noreply.github.com>2007-06-04 11:40:11 +0000
commitf46d8ce4be009f2ab0c6e8fe63d9aae2d3a6ef89 (patch)
treee29bbbd09196b43ae960b581b045998547aa33f8
parentfb4cb297c3162c745b9b3e4a5e0988d071b79222 (diff)
downloadATCD-f46d8ce4be009f2ab0c6e8fe63d9aae2d3a6ef89.tar.gz
ChangeLogTag:Sun
-rw-r--r--TAO/ChangeLog7
-rw-r--r--TAO/docs/ORBEndpoint.html122
2 files changed, 68 insertions, 61 deletions
diff --git a/TAO/ChangeLog b/TAO/ChangeLog
index 49e47afb9a2..30251a73d98 100644
--- a/TAO/ChangeLog
+++ b/TAO/ChangeLog
@@ -1,3 +1,10 @@
+Mon Jun 4 11:37:42 UTC 2007 Douglas C. Schmidt <schmidt@dre.vanderbilt.edu>
+
+ * docs/ORBEndpoint.html: Updated the files to use
+ ORBListenEndpoint rather than ORBEndpoint. Thanks to Vikram
+ Karandikar" <softking at gmail dot com> for motivating this
+ change.
+
Mon Jun 4 02:56:02 UTC 2007 Phil Mesnier <mesnier_p@ociweb.com>
* orbsvcs/tests/EC_MT_Mcast/MCast.cpp:
diff --git a/TAO/docs/ORBEndpoint.html b/TAO/docs/ORBEndpoint.html
index cde897c4245..afe5772ed93 100644
--- a/TAO/docs/ORBEndpoint.html
+++ b/TAO/docs/ORBEndpoint.html
@@ -4,12 +4,12 @@
<html>
<head>
- <title>-ORBEndpoint Details</title>
+ <title>-ORBListenEndpoint Details</title>
<!-- Changed by: , 12-Jun-2002 -->
</head>
<body text = "#000000" link="#000fff" vlink="#ff0f0f" bgcolor="#ffffff">
- <h1><A HREF="Options.html#-ORBEndpoint">-ORBEndpoint</A> Details</h1>
+ <h1><A HREF="Options.html#-ORBListenEndpoint">-ORBListenEndpoint</A> Details</h1>
<P>
<UL>
<LI><A HREF="#Overview">Overview</A></LI>
@@ -35,14 +35,14 @@
iiop://<I><EM>hostname</EM></I>:<I><EM>port</EM></I>
</CODE></blockquote>
Sets of endpoints may be specified using multiple
- <CODE>-ORBEndpoint</CODE> options or by delimiting endpoints with
+ <CODE>-ORBListenEndpoint</CODE> options or by delimiting endpoints with
a semi-colon (;). For example:
<blockquote><CODE>
- -ORBEndpoint iiop://localhost:9999 -ORBEndpoint uiop:///tmp/mylocalsock -ORBEndpoint shmiop://10002
+ -ORBListenEndpoint iiop://localhost:9999 -ORBListenEndpoint uiop:///tmp/mylocalsock -ORBListenEndpoint shmiop://10002
</CODE></blockquote>
is equivalent to:
<blockquote><CODE>
- -ORBEndpoint 'iiop://localhost:9999;uiop:///tmp/mylocalsock;shmiop://10002'
+ -ORBListenEndpoint 'iiop://localhost:9999;uiop:///tmp/mylocalsock;shmiop://10002'
</CODE></blockquote>
Notice the single quotes (') in the latter option specification.
Single quotes are needed to prevent the shell from interpreting
@@ -51,7 +51,7 @@
If an endpoint is specified without an <CODE>addr</CODE> such as
the following:
<blockquote><CODE>
- -ORBEndpoint uiop:// -ORBEndpoint shmiop://
+ -ORBListenEndpoint uiop:// -ORBListenEndpoint shmiop://
</CODE></blockquote>
then a default endpoint will be created for the specified protocol.
<P>
@@ -61,14 +61,14 @@
<P>
<h2><A NAME="Options">Endpoint-Specific Options</A></h2>
<P>
- The <CODE>-ORBEndpoint</CODE> options can accept
+ The <CODE>-ORBListenEndpoint</CODE> options can accept
endpoint-specific options. Specifically, such options will only
apply to the endpoint for which they were specified.
<P>
An endpoint-specific option is used as follows:
<BLOCKQUOTE>
<CODE>
- -ORBEndpoint iiop://foo:1234/option=value
+ -ORBListenEndpoint iiop://foo:1234/option=value
</CODE>
</BLOCKQUOTE>
<P>
@@ -76,7 +76,7 @@
with an ampersand '<CODE>&amp;</CODE>' as follows:
<BLOCKQUOTE>
<CODE>
- -ORBEndpoint 'iiop://foo:1234/option1=value1&option2=value2'
+ -ORBListenEndpoint 'iiop://foo:1234/option1=value1&option2=value2'
</CODE>
</BLOCKQUOTE>
<P>
@@ -102,7 +102,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://V.v@hostname1:port1,...,W.w@hostname2:port2
+ -ORBListenEndpoint iiop://V.v@hostname1:port1,...,W.w@hostname2:port2
</CODE>
</BLOCKQUOTE>
<P>
@@ -119,7 +119,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://hostname:port/foobar=50
+ -ORBListenEndpoint iiop://hostname:port/foobar=50
</CODE>
</BLOCKQUOTE>
<P>
@@ -144,14 +144,14 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://foo2
+ -ORBListenEndpoint iiop://foo2
</CODE>
</BLOCKQUOTE>
or:
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://foo2.bar.baz
+ -ORBListenEndpoint iiop://foo2.bar.baz
</CODE>
</BLOCKQUOTE>
<P>
@@ -167,7 +167,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://foo2:1234
+ -ORBListenEndpoint iiop://foo2:1234
</CODE>
</BLOCKQUOTE>
<P>
@@ -184,7 +184,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://foo2:my_protocol
+ -ORBListenEndpoint iiop://foo2:my_protocol
</CODE>
</BLOCKQUOTE>
<P>
@@ -201,7 +201,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://
+ -ORBListenEndpoint iiop://
</CODE>
</BLOCKQUOTE>
<P>
@@ -221,7 +221,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://:1234
+ -ORBListenEndpoint iiop://:1234
</CODE>
</BLOCKQUOTE>
<P>
@@ -240,7 +240,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://192.168.10.24:1234
+ -ORBListenEndpoint iiop://192.168.10.24:1234
</CODE>
</BLOCKQUOTE>
@@ -253,8 +253,8 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://[01ef::1]:123
- -ORBEndpoint iiop://[01ef::1:123]
+ -ORBListenEndpoint iiop://[01ef::1]:123
+ -ORBListenEndpoint iiop://[01ef::1:123]
</CODE>
</BLOCKQUOTE>
@@ -265,7 +265,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint iiop://1.1@[01ef::1]:123 <B><FONT color='RED'>--> ILLEGAL</FONT></B>
+ -ORBListenEndpoint iiop://1.1@[01ef::1]:123 <B><FONT color='RED'>--> ILLEGAL</FONT></B>
</CODE>
</BLOCKQUOTE>
<P>
@@ -297,10 +297,10 @@
ephemeral ports except within a restricted user-defined
range.
<P>
- The format for <CODE>ORBEndpoint</CODE> with the
+ The format for <CODE>ORBListenEndpoint</CODE> with the
<CODE>portspan</CODE> option is:
<BLOCKQUOTE>
- <CODE>-ORBEndpoint iiop://[</CODE><I>hostname</I><CODE>]:</CODE><I
+ <CODE>-ORBListenEndpoint iiop://[</CODE><I>hostname</I><CODE>]:</CODE><I
>initialPort</I><CODE>/portspan=</CODE><I>span</I>
</BLOCKQUOTE>
where <I>initialPort</I> is the initial port number in the
@@ -334,10 +334,10 @@
environments where the hostname in use is one whose IP
address changes dynamically.
<P>
- The format for <CODE>ORBEndpoint</CODE> with the
+ The format for <CODE>ORBListenEndpoint</CODE> with the
<CODE>hostname_in_ior</CODE> option is:
<BLOCKQUOTE>
- <CODE>-ORBEndpoint iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
+ <CODE>-ORBListenEndpoint iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
>port</I><CODE>/hostname_in_ior=</CODE><I>overridden_hostname</I>
</BLOCKQUOTE>
where <I>local_hostname</I> and <I>port</I> are specified
@@ -362,10 +362,10 @@
platforms (e.g. Solaris 5.7 x86 allows programs run as same or different
users to bind to the same port when SO_REUSEADDR is set by all users).
<P>
- The format for <CODE>ORBEndpoint</CODE> with the
+ The format for <CODE>ORBListenEndpoint</CODE> with the
<CODE>reuse_addr</CODE> option is:
<BLOCKQUOTE>
- <CODE>-ORBEndpoint iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
+ <CODE>-ORBListenEndpoint iiop://[</CODE><I>local_hostname</I><CODE>]:</CODE><I
>port</I><CODE>/reuse_addr=[0|1]</CODE>
</BLOCKQUOTE>
</TD>
@@ -377,16 +377,16 @@
<P>
Here are some additional examples of IIOP endoints:
<UL>
- <LI><CODE>-ORBEndpoint iiop://1.0@foo1:0</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.0@foo:0,1.1@bar,baz:3456</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.0@foo:0,1.1@bar,baz:3456/foobar=300</CODE></LI>
- <LI><CODE>-ORBEndpoint iiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
- <LI><CODE>-ORBEndpoint iiop://:2020/foobar=12345</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.1@</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.1@:1234</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.1@,1.0@:1234,1.1@</CODE>
- <LI><CODE>-ORBEndpoint iiop://1.1@foo:2020/portspan=30</CODE>
- <LI><CODE>-ORBEndpoint iiop://foo:2020 -ORBEndpoint iiop://foo:10020 </CODE> </CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.0@foo1:0</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.0@foo:0,1.1@bar,baz:3456</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.0@foo:0,1.1@bar,baz:3456/foobar=300</CODE></LI>
+ <LI><CODE>-ORBListenEndpoint iiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
+ <LI><CODE>-ORBListenEndpoint iiop://:2020/foobar=12345</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.1@:1234</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.1@,1.0@:1234,1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://1.1@foo:2020/portspan=30</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://foo:2020 -ORBListenEndpoint iiop://foo:10020 </CODE> </CODE>
</UL>
<hr>
@@ -402,7 +402,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint shmiop://V.v@port1,...,W.w@port2
+ -ORBListenEndpoint shmiop://V.v@port1,...,W.w@port2
</CODE>
</BLOCKQUOTE>
<P>
@@ -429,7 +429,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint shmiop://
+ -ORBListenEndpoint shmiop://
</CODE>
</BLOCKQUOTE>
<P>
@@ -441,14 +441,14 @@
<P>
Here are some additional examples of SHMIOP endoints:
<UL>
- <LI><CODE>-ORBEndpoint shmiop://1.0@0</CODE>
- <LI><CODE>-ORBEndpoint shmiop://1.0@0,3456</CODE>
- <LI><CODE>-ORBEndpoint shmiop://1.0@0,3456/foobar=300</CODE></LI>
- <LI><CODE>-ORBEndpoint shmiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
- <LI><CODE>-ORBEndpoint shmiop://2020/foobar=12345</CODE>
- <LI><CODE>-ORBEndpoint shmiop://1.1@</CODE>
- <LI><CODE>-ORBEndpoint shmiop://1.1@1234</CODE>
- <LI><CODE>-ORBEndpoint shmiop://1.1@,1.0@1234,1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.0@0</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.0@0,3456</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.0@0,3456/foobar=300</CODE></LI>
+ <LI><CODE>-ORBListenEndpoint shmiop:///foobar=2</CODE> <FONT COLOR=RED>(notice three slashes "<CODE>///</CODE>")</FONT>
+ <LI><CODE>-ORBListenEndpoint shmiop://2020/foobar=12345</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.1@1234</CODE>
+ <LI><CODE>-ORBListenEndpoint shmiop://1.1@,1.0@1234,1.1@</CODE>
</UL><p>
You <font color="red">must specify the hostname</font>, however,
@@ -477,7 +477,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint uiop://V.v@rendezvous_point1,...,W.w@rendezvous_point2
+ -ORBListenEndpoint uiop://V.v@rendezvous_point1,...,W.w@rendezvous_point2
</CODE>
</BLOCKQUOTE>
<P>
@@ -494,7 +494,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint 'uiop://1.0@/tmp/my_rendezvous_point|foobar=50'
+ -ORBListenEndpoint 'uiop://1.0@/tmp/my_rendezvous_point|foobar=50'
</CODE>
</BLOCKQUOTE>
<P>
@@ -518,7 +518,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint uiop:///tmp/foobar
+ -ORBListenEndpoint uiop:///tmp/foobar
</CODE>
</BLOCKQUOTE>
In this example, the optional protocol version and
@@ -529,7 +529,7 @@
path could be:
<BLOCKQUOTE>
<P>
- <CODE>-ORBEndpoint uiop://foobar</CODE> <FONT COLOR=RED>(DISCOURAGED)</FONT>
+ <CODE>-ORBListenEndpoint uiop://foobar</CODE> <FONT COLOR=RED>(DISCOURAGED)</FONT>
</BLOCKQUOTE>
<P>
Again, rendezvous points with relative paths are discouraged
@@ -542,7 +542,7 @@
<BLOCKQUOTE>
<P>
<CODE>
- -ORBEndpoint uiop://
+ -ORBListenEndpoint uiop://
</CODE>
</BLOCKQUOTE>
<P>
@@ -556,12 +556,12 @@
<P>
Here are some additional examples of UIOP endoints:
<UL>
- <LI><CODE>-ORBEndpoint uiop://1.0@/tmp/foo1</CODE>
- <LI><CODE>-ORBEndpoint uiop://1.0@/tmp/foo,1.1@/home/bar/baz</CODE>
- <LI><CODE>-ORBEndpoint 'uiop://1.1@/tmp/bar|foobar=300'</CODE></LI>
- <LI><CODE>-ORBEndpoint 'uiop://|foobar=2'</CODE>
- <LI><CODE>-ORBEndpoint uiop://1.1@</CODE>
- <LI><CODE>-ORBEndpoint uiop://1.1@,1.0@/tmp/foo,1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint uiop://1.0@/tmp/foo1</CODE>
+ <LI><CODE>-ORBListenEndpoint uiop://1.0@/tmp/foo,1.1@/home/bar/baz</CODE>
+ <LI><CODE>-ORBListenEndpoint 'uiop://1.1@/tmp/bar|foobar=300'</CODE></LI>
+ <LI><CODE>-ORBListenEndpoint 'uiop://|foobar=2'</CODE>
+ <LI><CODE>-ORBListenEndpoint uiop://1.1@</CODE>
+ <LI><CODE>-ORBListenEndpoint uiop://1.1@,1.0@/tmp/foo,1.1@</CODE>
</UL>
<hr>
@@ -590,8 +590,8 @@
<P>
Here are some additional examples of DIOP endoints:
<UL>
- <LI><CODE>-ORBEndpoint diop://1.0@foo1:2345</CODE>
- <LI><CODE>-ORBEndpoint diop://1.1@:1234</CODE>
+ <LI><CODE>-ORBListenEndpoint diop://1.0@foo1:2345</CODE>
+ <LI><CODE>-ORBListenEndpoint diop://1.1@:1234</CODE>
</UL>
<hr>
@@ -619,7 +619,7 @@
port use the <CODE>ssl_port</CODE> endpoint option:
<UL>
- <LI><CODE>-ORBEndpoint iiop://foo:1234/ssl_port=1235</CODE>
+ <LI><CODE>-ORBListenEndpoint iiop://foo:1234/ssl_port=1235</CODE>
</UL>
In this case, an <A HREF="#IIOP">IIOP</A> endpoint would be opened