summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohnny Willemsen <jwillemsen@remedy.nl>2018-04-04 11:03:29 +0200
committerJohnny Willemsen <jwillemsen@remedy.nl>2018-04-04 11:03:29 +0200
commit110a761b4731a561fbc04a62f98bc35863d4a64f (patch)
treef638690e4f9dcd7cdfa7939144f0425c5f98597d
parentf08ccbcc82b9b835cf5cac41a8095e2219d6243d (diff)
downloadATCD-110a761b4731a561fbc04a62f98bc35863d4a64f.tar.gz
Minor documentation changes and remove old cvs date tags
-rw-r--r--ACE/contrib/FaCE/FaCE.cpp1
-rw-r--r--TAO/docs/cec_options.html8
-rw-r--r--TAO/docs/documentation.html2
-rw-r--r--TAO/docs/releasenotes/PSS.html2
-rw-r--r--TAO/docs/releasenotes/TODO.html4
-rw-r--r--TAO/docs/releasenotes/amh.html77
-rw-r--r--TAO/docs/releasenotes/ec.html1
-rw-r--r--TAO/docs/releasenotes/index.html21
-rw-r--r--TAO/docs/releasenotes/orbcore.html1
-rw-r--r--TAO/docs/rtcorba/architecture.html1
-rw-r--r--TAO/docs/rtcorba/faq.html2
-rw-r--r--TAO/docs/rtcorba/features.html4
-rw-r--r--TAO/docs/rtcorba/issues.html2
-rw-r--r--TAO/docs/rtcorba/omg_issues.html4
-rw-r--r--TAO/docs/rtcorba/status.html2
15 files changed, 47 insertions, 85 deletions
diff --git a/ACE/contrib/FaCE/FaCE.cpp b/ACE/contrib/FaCE/FaCE.cpp
index 22eeadc1e13..bbe83ebca91 100644
--- a/ACE/contrib/FaCE/FaCE.cpp
+++ b/ACE/contrib/FaCE/FaCE.cpp
@@ -26,7 +26,6 @@ const ACE_TCHAR* g_ParameterFileName = ACE_TEXT("Parameters.txt");
* parameters and parameter history file.
*
* @author Si Mong Park (spark@ociweb.com)
- * @version $Revision$ $Date$
*/
class ParameterList
{
diff --git a/TAO/docs/cec_options.html b/TAO/docs/cec_options.html
index e91ac919a4e..1e5db2f4db5 100644
--- a/TAO/docs/cec_options.html
+++ b/TAO/docs/cec_options.html
@@ -452,13 +452,5 @@ static CEC_Factory "-CECDispatching reactive ....."
<P><HR><P>
Back to the TAO <A HREF="index.html">components documentation</A>.
-
- <!--#include virtual="/~schmidt/cgi-sig.html" -->
-
- <address><a href="mailto:coryan@cs.wustl.edu">Carlos O'Ryan</a></address>
-<!-- Created: Thu Jul 1 21:44:28 CDT 1999 -->
-<!-- hhmts start -->
-Last modified: Fri Apr 20 15:24:09 CDT 2001
-<!-- hhmts end -->
</body>
</html>
diff --git a/TAO/docs/documentation.html b/TAO/docs/documentation.html
index 39e70620173..38bfe9d57db 100644
--- a/TAO/docs/documentation.html
+++ b/TAO/docs/documentation.html
@@ -25,7 +25,7 @@ bgcolor="#ffffff">
<dt> <img alt="o" src="redball.gif"> <a HREF="http://www.theaceorb.com/product/index.html">OCI TAO Developer's Guide</a> </dt><P>
- <dt> <img alt="o" src="redball.gif"> <a HREF="http://www.remedy.nl/opensource/corbapg.html">Remedy TAO Programmer's Guide</a> </dt><P>
+ <dt> <img alt="o" src="redball.gif"> <a HREF="https://www.remedy.nl/opensource/corbapg.html">Remedy IT CORBA Programmer's Guide</a> </dt><P>
<dt> <img alt="o" src="redball.gif"> <a HREF="orbsvcs.html">Online ORB Services Documentation</a> </dt><P>
diff --git a/TAO/docs/releasenotes/PSS.html b/TAO/docs/releasenotes/PSS.html
index 6b021fe8e06..de4907bf3ea 100644
--- a/TAO/docs/releasenotes/PSS.html
+++ b/TAO/docs/releasenotes/PSS.html
@@ -15,7 +15,7 @@
<p>Last Update: 2002/07/29 </p>
</center>
- <p>Persistent State Service (PSS) desribes a way of making a
+ <p>Persistent State Service (PSS) describes a way of making a
service persistent. The fact that PSS is being used by a
service is known only to the service (server) and not to the
client which makes use of the service. PSS presents persistent
diff --git a/TAO/docs/releasenotes/TODO.html b/TAO/docs/releasenotes/TODO.html
index 75e33df01e6..65e12cbc427 100644
--- a/TAO/docs/releasenotes/TODO.html
+++ b/TAO/docs/releasenotes/TODO.html
@@ -17,10 +17,6 @@
Bugzilla
</A> now.
</P>
- <P>
- Last Updated: $Date$ $Revision$
- </P>
-
<HR>
<P>Back to the TAO <A HREF="../index.html">documentation index</A>.&nbsp;<!--#include virtual="/~schmidt/cgi-sig.html" -->
diff --git a/TAO/docs/releasenotes/amh.html b/TAO/docs/releasenotes/amh.html
index 141d1a4eabe..556692c3d16 100644
--- a/TAO/docs/releasenotes/amh.html
+++ b/TAO/docs/releasenotes/amh.html
@@ -9,11 +9,10 @@
<h3>TAO's Asynchronous Method Handling (AMH) Feature</h3>
Point of contact: <a href="mailto:coryan@uci.edu">Carlos O'Ryan, </a>
<a href="mailto:mayur@ics.uci.edu">Mayur Deshpande</a>
- <h4>Last Updated: $Date$</h4>
- <p> The purpose of this document is to provide a guide to using the AMH
-capability available in TAO. This capability is not specified by any
-CORBA specification (as of date). This document lists the motivation for AMH,
+ <p> The purpose of this document is to provide a guide to using the AMH
+capability available in TAO. This capability is not specified by any
+CORBA specification (as of date). This document lists the motivation for AMH,
how to use it and its current implementation status. </p>
<HR SIZE=4 WIDTH="100%">
@@ -21,42 +20,42 @@ how to use it and its current implementation status. </p>
<h3>Context</h3>
For many types of distributed systems, the CORBA asynchronous method
-invocation
-<a href="index.html/#ami"> (AMI) </a>
-mechanism can improve concurrency, scalability, and
-responsiveness significantly. AMI allows clients to invoke multiple
+invocation
+<a href="index.html/#ami"> (AMI) </a>
+mechanism can improve concurrency, scalability, and
+responsiveness significantly. AMI allows clients to invoke multiple
two-way requests without waiting for responses. The time normally
spent waiting for replies can therefore be used to perform other
-useful work. The TAO asynchronous method handling (AMH) is a
-mechanism, which extends the concepts of AMI from clients to
-servers. Servers with AMH capability can return immediately
-from (potentially) long, blocking requests. This makes the
-servers capable of higher throughput. For a detailed description
-for the motivation and potential use-cases of AMH, please refer to
+useful work. The TAO asynchronous method handling (AMH) is a
+mechanism, which extends the concepts of AMI from clients to
+servers. Servers with AMH capability can return immediately
+from (potentially) long, blocking requests. This makes the
+servers capable of higher throughput. For a detailed description
+for the motivation and potential use-cases of AMH, please refer to
<a href="http://www.cs.wustl.edu/~schmidt/PDF/AMH.pdf">AMH-Motivation. </a>
<HR SIZE=4 WIDTH="100%">
<h3>Using AMH</h3>
-Servers that want to take advantage of AMH capability must use
-AMH-servants derived from AMH-skeletons. Invoking the
+Servers that want to take advantage of AMH capability must use
+AMH-servants derived from AMH-skeletons. Invoking the
<a href="index.html#idl">IDL-Compiler </a>
with the "-GH" option causes the IDL-Compiler to generate
-AMH-skeletons for all interfaces in the ".idl" file. The signatures
-of the AMH-methods differ from the original interfaces as per the
-rules described in
+AMH-skeletons for all interfaces in the ".idl" file. The signatures
+of the AMH-methods differ from the original interfaces as per the
+rules described in
<a href="http://www.cs.wustl.edu/~schmidt/PDF/DOA-02.pdf"">AMH-In-Detail. </a>
-Servants derived from the AMH-skeletons are registered with the POA in the usual manner
-and appear to clients as "normal" servants for the corresponding
-interfaces; Thus even while being transparent to the client, these
-servants are now capable of handling requests asynchronously.
-AMH-servants can be registered in any POA and can intermix with
-"normal" servants in the same POA. The granularity of AMH is at
+Servants derived from the AMH-skeletons are registered with the POA in the usual manner
+and appear to clients as "normal" servants for the corresponding
+interfaces; Thus even while being transparent to the client, these
+servants are now capable of handling requests asynchronously.
+AMH-servants can be registered in any POA and can intermix with
+"normal" servants in the same POA. The granularity of AMH is at
the interface level and not at the method level; Thus for an interface
-compiled with the "-GH" option, all operations in that interface are
+compiled with the "-GH" option, all operations in that interface are
asynchronous. Currently, AMH doesn't work in conjunction with
-<a href="index.html#interceptor">Interceptors </a>
+<a href="index.html#interceptor">Interceptors </a>
and behaviour is undefined if both are used together.
<HR SIZE=4 WIDTH="100%">
@@ -73,7 +72,7 @@ and behaviour is undefined if both are used together.
<li>Generation of AMH ResponseHandlers.</li>
<li>AMH Exceptions.</li>
<li>Fix the narrow method bug for AMH skeletons : Fixed
-<li>Sending intelligent exception codes back to client in case
+<li>Sending intelligent exception codes back to client in case
something nasty happens in the AMH server.</li>
<li>Example of using AMH available at ACE_wrappers/TAO/examples/AMH/Sink_Server.</li>
<li>Test for AMH : ACE_wrappers/TAO/performance-tests/Latency/AMH</li>
@@ -85,17 +84,17 @@ something nasty happens in the AMH server.</li>
<h3>Credits</h3>
-Original idea first proposed by
-<a href="mailto:coryan@uci.edu">Carlos O'Ryan </a>
-and changes to ORB for AMH first attempted by
-<a href="mailto:brucetrask@aol.com">Bruce Trask. </a>
-First go to get the IDL-Compiler to generate AMH code attempted by
-<a href="mailto:brunsch@doc.ece.uci.edu"> Darrell Brunsch. </a>
-ORB changes for AMH as they stand today put in by
-<a href="mailto:mayur@ics.uci.edu">Mayur Deshpande. </a>
-Second go at getting IDL-compiler to generate code attempted by Mayur and
-<a href="mailto:parsons@cs.wustl.edu">Jeff Parsons. </a>
-Getting the IDL-Compiler beast to generate the right AMH code finally
+Original idea first proposed by
+<a href="mailto:coryan@uci.edu">Carlos O'Ryan </a>
+and changes to ORB for AMH first attempted by
+<a href="mailto:brucetrask@aol.com">Bruce Trask. </a>
+First go to get the IDL-Compiler to generate AMH code attempted by
+<a href="mailto:brunsch@doc.ece.uci.edu"> Darrell Brunsch. </a>
+ORB changes for AMH as they stand today put in by
+<a href="mailto:mayur@ics.uci.edu">Mayur Deshpande. </a>
+Second go at getting IDL-compiler to generate code attempted by Mayur and
+<a href="mailto:parsons@cs.wustl.edu">Jeff Parsons. </a>
+Getting the IDL-Compiler beast to generate the right AMH code finally
achieved by Carlos.
<HR SIZE=4 WIDTH="100%">
diff --git a/TAO/docs/releasenotes/ec.html b/TAO/docs/releasenotes/ec.html
index 3a6a3bca6cb..43c142707db 100644
--- a/TAO/docs/releasenotes/ec.html
+++ b/TAO/docs/releasenotes/ec.html
@@ -8,7 +8,6 @@
<H3>TAO's Real-time Event Service</H3>
Point of contact: <A HREF="mailto:jwillemsen@remedy.nl">Johnny Willemsen</A>
- <H4>Last Updated: $Date$</H4>
Documentation for the command line and service configurator
options used to configure the real-time event service is available <A
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index a529c8898a2..f676bdf3c39 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -185,24 +185,6 @@ Notification Service
</td>
<td VALIGN=TOP>
-<ul>
-<b>CCM Related</b>
-<br><BR>
-<li>
-<a href="../../../CIAO/docs/releasenotes/index.html">CORBA Component Model (CIAO)</a></li>
-<li>
-<a href="../../../CIAO/docs/releasenotes/dance.html">Deployment and
- Configuration Engine (DAnCE)</a></li>
-<li>
-<a href="../../../CIAO/CIDLC/README.html">Component Implementation
-Definition Language Compiler (CIDLC)</a></li>
-<li>
-<a href="../../../CIAO/docs/static_ciao_contents.html">Static Configuration
- Support for Real-Time Platforms</a></li>
-</ul>
-</td>
-
-<td VALIGN=TOP>
</td>
</tr>
</table>
@@ -215,7 +197,7 @@ Definition Language Compiler (CIDLC)</a></li>
</table>
-A complete list of all modifications to TAO is available in the <a href="../../ChangeLog">ChangeLog</a>.
+A complete list of all modifications to TAO is available in the <a href="../../ChangeLogs">ChangeLogs</a>.
<p>
<hr>
<h3>
@@ -2555,6 +2537,5 @@ Need to test local object support more systematically and comprehensively.
<hr>
<p>Back to the TAO <a href="../index.html">documentation index</a>.<!--#include virtual="/~schmidt/cgi-sig.html" -->
-<hr><!-- hhmts start -->Last modified: Thu May 4 13:08:35 UTC 2006<!-- hhmts end -->
</body>
</html>
diff --git a/TAO/docs/releasenotes/orbcore.html b/TAO/docs/releasenotes/orbcore.html
index 611fb321c69..60aad951879 100644
--- a/TAO/docs/releasenotes/orbcore.html
+++ b/TAO/docs/releasenotes/orbcore.html
@@ -23,7 +23,6 @@
Point of contact: <a href="mailto: bala@cs.wustl.edu">Balchandran Natarajan</a>
-<p>Last Update: $Date$</p>
</center>
<!-- ============================================================ -->
diff --git a/TAO/docs/rtcorba/architecture.html b/TAO/docs/rtcorba/architecture.html
index a88c762f940..b160c6fb7cf 100644
--- a/TAO/docs/rtcorba/architecture.html
+++ b/TAO/docs/rtcorba/architecture.html
@@ -112,6 +112,5 @@ and deposit the requests into the right queue for processing.&nbsp;&nbsp;</p>
is an easier design to implement, integrate and test piece-by-piece.</li>
</ul>
<hr>
-<p><i>Last modified: $Date$</i></p>
</body>
</html>
diff --git a/TAO/docs/rtcorba/faq.html b/TAO/docs/rtcorba/faq.html
index ac0ec52cfb4..efd90ea90c7 100644
--- a/TAO/docs/rtcorba/faq.html
+++ b/TAO/docs/rtcorba/faq.html
@@ -33,8 +33,6 @@
<hr>
<i>
-<p>Last modified: $Date$ </i></p>
-
<p>&nbsp;</p>
</body>
</html>
diff --git a/TAO/docs/rtcorba/features.html b/TAO/docs/rtcorba/features.html
index a8d1edc5d3b..c1a16aa8f28 100644
--- a/TAO/docs/rtcorba/features.html
+++ b/TAO/docs/rtcorba/features.html
@@ -208,7 +208,7 @@ ThreadPools are now fully supported. Endpoint priorities are no longer
supported.</li>
<li>
By default dynamic RTCorba threads live forever after they are created.
-When using the <code>RTORBDynamicThreadIdleTimeout</code> from the
+When using the <code>RTORBDynamicThreadIdleTimeout</code> from the
<code>RT_ORB_Loader</code> it
can be specified that the dynamic threads should end after a given
idle time. Timeout must be specified in microseconds, 0 means the threads
@@ -838,7 +838,7 @@ priority</tt>
map the RTCORBA priority to the network priority.
</ul>
<br>
-<i>Last Modified: $Date$</i></dl>
+</dl>
</body>
</html>
diff --git a/TAO/docs/rtcorba/issues.html b/TAO/docs/rtcorba/issues.html
index 9aadf5c3eb6..c94a48f40ef 100644
--- a/TAO/docs/rtcorba/issues.html
+++ b/TAO/docs/rtcorba/issues.html
@@ -225,7 +225,7 @@ the guidelines are followed, of course ;-) )</p>
<i>
-<p>Last modified: $Date$ </i></p>
+</p>
<p></p>
</body>
</html>
diff --git a/TAO/docs/rtcorba/omg_issues.html b/TAO/docs/rtcorba/omg_issues.html
index 33316e69210..381d0d2a840 100644
--- a/TAO/docs/rtcorba/omg_issues.html
+++ b/TAO/docs/rtcorba/omg_issues.html
@@ -25,7 +25,7 @@ Unnecessary <i>ClientProtocolPolicy</i> complexity</h3>
in CORBA 2.4 cautions against defining policies that can be set
in both places:&nbsp;
<blockquote><br>
- If the <b><font FACE="Arial" SIZE="2">Policy </font></b> can be
+ If the <b><font FACE="Arial" SIZE="2">Policy </font></b> can be
used with <b><font FACE="Arial" SIZE="2">POA </font></b>creation
to tune <b><font FACE="Arial" SIZE="2">IOR </font></b>contents
and can also be specified (overridden) in the client, specify how to reconcile the policy's
@@ -98,6 +98,6 @@ provide different semantics or be invalid when used in another ORB, with both
ORBs being compliant with the specification.&nbsp;&nbsp;&nbsp; </p>
<hr>
-<p><i>Last Modified: $Date$</i></p>
+</p>
</body>
</html>
diff --git a/TAO/docs/rtcorba/status.html b/TAO/docs/rtcorba/status.html
index 54be0cc28aa..6bb5549cbc7 100644
--- a/TAO/docs/rtcorba/status.html
+++ b/TAO/docs/rtcorba/status.html
@@ -126,6 +126,6 @@ for their implementation:
<hr>
<i>
-<p>Last modified: $Date$</i></p>
+</p>
</body>
</html>