summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authornanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2003-03-22 22:51:15 +0000
committernanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2003-03-22 22:51:15 +0000
commitc1c7441dc025868e355dd7978ff45ecb98a571af (patch)
treedc6c11095759f95ecf68471b2350ce949a2a59a9
parent05aab858a84cb63b55d9617a4b53dbaa689e5f64 (diff)
downloadATCD-c1c7441dc025868e355dd7978ff45ecb98a571af.tar.gz
ChangeLogTag:Sat Mar 22 16:47:39 2003 Nanbor Wang <nanbor@cs.wustl.edu>
-rw-r--r--TAO/ChangeLog9
-rw-r--r--TAO/docs/ORBEndpoint.html28
2 files changed, 19 insertions, 18 deletions
diff --git a/TAO/ChangeLog b/TAO/ChangeLog
index a05313c6667..1d914d26bef 100644
--- a/TAO/ChangeLog
+++ b/TAO/ChangeLog
@@ -1,3 +1,10 @@
+Sat Mar 22 16:47:39 2003 Nanbor Wang <nanbor@cs.wustl.edu>
+
+ * docs/ORBEndpoint.html: Updated obsolete SHMIOP endpoint
+ information, and added more information when using shmiop with
+ interoperable naming service. Thanks to Andreas Koehler
+ <Andreas.Koehler@sysde.eads.net> for reporting the problem.
+
Sat Mar 22 15:51:14 2003 Jeff Parsons <j.parsons@vanderbilt.edu>
* tao/CurrentC.cpp:
@@ -25,7 +32,7 @@ Sat Mar 22 12:55:16 2003 Jeff Parsons <j.parsons@vanderbilt.edu>
* orbsvcs/IFR_Service/ifr_adding_visitor.cpp:
- Changed loading of constant into the repository to be aware
+ Changed loading of constant into the repository to be aware
if the constant's type is a typedef.
Sat Mar 22 07:41:59 2003 Phil Mesnier <mesnier_p@ociweb.com>
diff --git a/TAO/docs/ORBEndpoint.html b/TAO/docs/ORBEndpoint.html
index 2b18bfe826b..14e1d237ea3 100644
--- a/TAO/docs/ORBEndpoint.html
+++ b/TAO/docs/ORBEndpoint.html
@@ -338,7 +338,7 @@
<P>
<h3>SHMIOP Endpoint Overview</h3>
<P>
- SHMIOP endpoints in TAO have the form:
+ SHMIOP endpoints in TAO have the similar form to IIOP endpoints:
<BLOCKQUOTE>
<P>
<CODE>
@@ -348,21 +348,9 @@
<P>
Where "<CODE>V.v</CODE>" and "<CODE>W.w</CODE>" are the SHMIOP
protocol versions associated with the given address
- (port). Currently supported versions are <CODE>1.0</CODE> and
- <CODE>1.1</CODE>.
+ (port). Currently supported versions are <CODE>1.0</CODE>,
+ <CODE>1.1</CODE>, and <CODE>1.2</CODE>.
- <P>
- Options are separated from the addresses by a forward slash
- '<CODE>/</CODE>'. For instance, if an IIOP endpoint should have
- a property foobar of 50 associated with it, then the following
- endpoint specification could be used
- <BLOCKQUOTE>
- <P>
- <CODE>
- -ORBEndpoint shmiop://port/foobar=50
- </CODE>
- </BLOCKQUOTE>
- <P>
<h3>SHMIOP Address Format</h3>
<P>
SHMIOP addresses are comprised of a port number that the server
@@ -401,7 +389,13 @@
<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>
- </UL>
+ </UL><p>
+
+ You <font color="red">must specify the hostname</font>, however,
+ when using SHMIOP with <a href="INS.html">Interoperable Naming
+ Service</a> as you would with IIOP. This is because SHMIOP uses
+ the hostname to determine the validity of an endpoint. That is,
+ it will not try to connect to a remote SHMIOP endpoint locally.<p>
<hr>
@@ -534,7 +528,7 @@
<address><a href="mailto:ossama@uci.edu">Ossama Othman</a></address>
<!-- Created: Thu May 18 08:37:25 PDT 2000 -->
<!-- hhmts start -->
-Last modified: Sat Jun 15 11:30:52 CDT 2002
+Last modified: Sat Mar 22 16:47:36 Central Standard Time 2003
<!-- hhmts end -->
</body>
</html>