ChangeLogTag:Wed Oct 20 00:05:34 1999 Douglas C. Schmidt <schmidt@tango.cs.wustl.edu>

4 files changed, 20 insertions, 19 deletions

diff --git a/TAO/docs/exceptions.html b/TAO/docs/exceptions.html
index 8999b2f4aba..f847bd780ef 100644
--- a/TAO/docs/exceptions.html
+++ b/TAO/docs/exceptions.html
@@ -9,11 +9,11 @@
 <h1>Exception Handling</h1>
 
 Since the exception handling macros in TAO can be used with any ORB,
-it has been generalized and moved to ACE.
+they have been generalized and moved to ACE. <P>
 
-<h3>Notice that ACE's try macros are now prefered over the original
-TAO try macros.  You should avoid using them in your applications.
-They might be removed completely one day.</h3>
+<h3>Note that ACE's try macros are now prefered over the original TAO
+try macros.  You should avoid using them in your applications.  They
+might be removed completely one day.</h3>
 
 The new document about exception handling has been moved to
 <a href="../../docs/exceptions.html">here</a>.
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index 0cbd9cb87f6..ad8c664322f 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -631,7 +631,7 @@ system.  This specification builds on the CORBA Architecture
 Specification version 2.2 and the CORBA Messaging Specification.
 Primarily, RT-CORBA adds to the Policy framework defined in the
 Messaging specification and adds to GIOP/IIOP version 1.1 to support
-these extensions.
+these extensions. <P>
 
 This effort will implement the RT-CORBA specification and required
 parts of the Messaging specification.  Our implementation of RT-CORBA
@@ -639,7 +639,7 @@ in TAO will occur in stages.  Our initial focus will be the support of
 statically configured, real-time embedded systems where it is possible
 to eliminate many sources of unbounded priority inversion.  This will
 be followed by a more general implementation which supports more
-dynamic environments and scheduling mechanisms.
+dynamic environments and scheduling mechanisms. <P>
 
 Support for statically configured applications requires a framework
 which allows for explicit mappings between CORBA priorities,
@@ -650,7 +650,7 @@ Essentially, applications are able to assign priorities to connections
 between server and client, then using the existing Policy framework
 along with new Policy objects, requests are routed to the appropriate
 connections.  By assigning equivalent thread and object priorities,
-applications are able to ensure end-to-end priority preservation.
+applications are able to ensure end-to-end priority preservation. <P>
 
 As a part of this initial effort we are also adding support for both
 reliable and buffered oneway operations.  Reliable oneway operations
@@ -659,7 +659,7 @@ method for providing different levels of support for reliable message
 delivery. Traditional oneway semantics are unacceptable in many
 environments.  For example, there is no guarantee that a particular
 invocation will actually be delivered.  Additionally, location
-forwarding will not occur with traditional oneway invocations.
+forwarding will not occur with traditional oneway invocations. <P>
 
 <P>
 The Messaging specification has defined four alternative
@@ -670,7 +670,7 @@ Policy from the Messaging Specification is used to specify the level of
 reliability required.  The policy is set on the client side and uses a
 new flags field in the GIOP 1.2 header.  The server checks this flag to
 determine if a reply is required for the oneway invocation.  Four
-different levels synchronization are defined in the RT specification:
+different levels synchronization are defined in the RT specification: 
 
         <p>
         <ul>
@@ -743,7 +743,7 @@ different priorities directly contributes to maintaining end-to-end
 priority in a distributed system.  Please see TAO/tao/TAO.idl for
 ClientPriorityPolicy interface, and TAO/tests/Endpoint_Per_Priority for
 its use.  Current implementation does not work properly in presence of
-location forward messages.
+location forward messages. <P>
 
 </ul>
 Known issues:
diff --git a/TAO/docs/releasenotes/orbcore.html b/TAO/docs/releasenotes/orbcore.html
index 42c5fdb0a76..fe09fb039d6 100644
--- a/TAO/docs/releasenotes/orbcore.html
+++ b/TAO/docs/releasenotes/orbcore.html
@@ -147,6 +147,7 @@ Point of contact: <a href="mailto: irfan@cs.wustl.edu">Irfan Pyarali</a>
       </ol>
 
   <li>Documentation:</li>
+    <ol>
         <li><p>Writing up ORB restructuring notes.</p>
         </li>
       </ol>
diff --git a/docs/exceptions.html b/docs/exceptions.html
index 312cf495d32..b297754a4a6 100644
--- a/docs/exceptions.html
+++ b/docs/exceptions.html
@@ -7,15 +7,9 @@
 <body text="#000000" link="#0000ff" vlink="#cc0000" bgcolor="#ffffff">
 <h1>Using ACE try macros for CORBA programming</h1>
 
-<p>ACE try macros will completely replace TAO try macros soon.  If you
-are still using TAO try macros in your code, you should replace them
-with ACE try macros to avoid possible breakage when we remove TAO try
-macros.<\p>
-
-<P>It would be useful if the reader can go through the book, "Advanced
-Corba Programming with C++" by Michi & Steve, from pages 307 through
-to 322.
-</P>
+<P>We recommend you check out pages 307 through to 322 in the book,
+"Advanced Corba Programming with C++" by Michi Henning & Steve Vinoski
+before reading this document.
 
 <P>CORBA::Environment provides a way to handle exceptions when
 native c++ exception handling is unavailable or undesirable.
@@ -521,5 +515,11 @@ Some of the problems that our macros are described below:
   </LI>
 </UL>
 
+<P><HR><P>
+
+Back to the <A
+HREF="http://www.cs.wustl.edu/~schmidt/ACE-documentation.html">ACE
+documentation</A> page.
+
 <!--#include virtual="/~schmidt/cgi-sig.html" -->
 </body></HTML>