Fixed various broken links

7 files changed, 63 insertions, 63 deletions

diff --git a/ACE/ace/Proactor.h b/ACE/ace/Proactor.h
index ec5cad27118..31c4aa2e210 100644
--- a/ACE/ace/Proactor.h
+++ b/ACE/ace/Proactor.h
@@ -122,7 +122,7 @@ protected:
  * @brief A manager for asynchronous event demultiplexing.
  *
  * See the Proactor pattern description at
- * http://www.cs.wustl.edu/~schmidt/proactor.ps.gz for more
+ * http://www.dre.vanderbilt.edu/~schmidt/PDF/proactor.pdf for more
  * details.
  */
 class ACE_Export ACE_Proactor
diff --git a/ACE/ace/Proactor_Impl.h b/ACE/ace/Proactor_Impl.h
index 9b27fcbde72..f8851eacab3 100644
--- a/ACE/ace/Proactor_Impl.h
+++ b/ACE/ace/Proactor_Impl.h
@@ -34,7 +34,7 @@ ACE_BEGIN_VERSIONED_NAMESPACE_DECL
  * classes.
  *
  * See the Proactor pattern description at
- * http://www.cs.wustl.edu/~schmidt/proactor.ps.gz for more
+ * http://www.dre.vanderbilt.edu/~schmidt/PDF/proactor.pdf for more
  * details.
  */
 class ACE_Export ACE_Proactor_Impl : public ACE_Event_Handler
diff --git a/ACE/docs/ACE-bug-process.html b/ACE/docs/ACE-bug-process.html
index 98117264d30..d727320f420 100644
--- a/ACE/docs/ACE-bug-process.html
+++ b/ACE/docs/ACE-bug-process.html
@@ -16,7 +16,7 @@ lists</A> has grown
 considerably.  While this increase is healthy, and a natural
 consequence of the larger number of ACE, TAO, and CIAO users, it is
 straining the resources of the researchers in the <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-members-i.html">DOC
+HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-members-i.html">DOC
 group</A> at <A
 HREF="http://www.cs.wustl.edu/~schmidt/doc-center.html">Washington
 University</A>, <A HREF="http://zen.uci.edu">UC Irvine</A> and <A
diff --git a/ACE/docs/ACE-lessons.html b/ACE/docs/ACE-lessons.html
index 0b1b066e77c..569d92fbaa5 100644
--- a/ACE/docs/ACE-lessons.html
+++ b/ACE/docs/ACE-lessons.html
@@ -14,7 +14,7 @@ bgcolor="#ffffff">
 <H3>Lessons Learned Building Reusable OO Telecommunication Software Frameworks</H3>
 
 <DT>Douglas C. Schmidt
-<DT>Department of Computer Science 
+<DT>Department of Computer Science
 <DT>Washington University, St. Louis
 <DT><A HREF="http://www.cs.wustl.edu/~schmidt/">http://www.cs.wustl.edu/~schmidt/</A>
 <DT><A HREF="mailto:schmidt@cs.wustl.edu">schmidt@cs.wustl.edu</A>
@@ -24,8 +24,8 @@ Express'' magazine, Vol. 4, No. 6, December, 1996. <P>
 
 <P><HR><P>
 
-<H3>The Distributed Software Crisis</H3>   
-  
+<H3>The Distributed Software Crisis</H3>
+
 Developing complex software systems is expensive and error-prone.
 Object-oriented (OO) programming languages [Stroustrup:91,Gosling:96],
 components [Box:97], and frameworks [Lewis:95] are heavily touted
@@ -94,12 +94,12 @@ art," often locked in the heads of expert developers. <P>
 <P><HR><P>
 
 <H3>Lessons Learned Building Reusable OO Communication Software Frameworks</H3>
-  
+
 Over the past decade, I've worked with many companies (including
 Motorola Iridium, Ericsson, Siemens, Bellcore, Kodak, and McDonnell
 Douglas) building reusable OO communication software [Schmidt:96].  In
 these projects, we've applied a range of OO middleware tools including
-OMG <A HREF="http://www.cs.wustl.edu/~schmidt/corba.html">CORBA</A>
+OMG <A HREF="http://www.dre.vanderbilt.edu/~schmidt/corba.html">CORBA</A>
 (an emerging industry standard for distributed object computing) and
 the <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE.html">ACE</A>
 framework (a widely used C++ framework that implements many strategic
@@ -111,7 +111,7 @@ practice: <P>
 <UL>
 <LI> <B><EM> Successful reuse-in-the-large requires non-technical
 prerequisites -- </EM></B><P>
-   
+
   Many political, economical, organizational, and psychological
   factors can impede successful reuse in telecom companies.  I've
   found that reuse-in-the-large works best when (1) the marketplace is
@@ -126,7 +126,7 @@ prerequisites -- </EM></B><P>
   syndrome and rebuild everything from scratch. <P>
 
 <LI> <B><EM> Iteration and incremental growth is essential </EM></B> -- <P>
-   
+
   Expanding on the corporate culture theme, I've observed that it's
   crucial for software managers to openly support the fact that good
   components, frameworks, and software architectures take time to
@@ -140,7 +140,7 @@ prerequisites -- </EM></B><P>
 
 <LI> <B><EM> Integrate infrastructure developers with application developers
 </EM></B> -- <P>
-   
+
   Truly useful components and frameworks are derived from solving real
   problems, e.g., telecommunications, medical imaging, avionics, OLTP,
   etc.  Therefore, a time honored way of producing reusable components
@@ -152,7 +152,7 @@ prerequisites -- </EM></B><P>
   won't solve real problems and will not be reused. <P>
 
 <LI> <B><EM> Industry ``standards'' are not panaceas -- </EM></B> <P>
-  
+
   Expecting emerging industry standards (like CORBA or TINA) to
   eliminate telecom software complexity today is very risky.  For
   instance, although some CORBA ORB implementations are suited for
@@ -163,20 +163,20 @@ prerequisites -- </EM></B><P>
   demanding real-time performance and reliability requirements in the
   telecom domain, over the next 2 years we'll see CORBA-based products
   emerge that support such features [Schmidt:96].<P>
-  
+
 <LI> <B><EM> Beware of simple(-minded) solutions to complex software problems
 -- </EM></B> <P>
-   
+
   Apply simple solutions to complex problems that sound too good to be
   true typically are...  For example, translating code entirely from
   high-level specifications or using trendy OO design methodologies
   and programming languages is no guarantee of success.  In my
   experience, there's simply no substitute for skilled software
   developers, which leads to the following final ``lesson learned.''
-<P>  
+<P>
 
 <LI> <B><EM> Respect and reward quality developers </EM></B> -- <P>
-   
+
   Ultimately, reusable components are only as good as the people who
   build and use them.  Developing robust, efficient, and reusable
   telecom middleware requires teams with a wide range of skills.  We
@@ -192,10 +192,10 @@ prerequisites -- </EM></B><P>
   companies who respect and reward their high quality software
   developers will increasingly outperform those who don't. <P>
 </UL>
-   
+
 <P><HR><P>
-<H3>Concluding Remarks</H3>  
-  
+<H3>Concluding Remarks</H3>
+
 Developing reusable OO middleware components and frameworks is not a
 silver bullet.  Software is inherently abstract, which makes it hard
 to engineer its quality and to manage its production.  The good news,
@@ -221,29 +221,29 @@ to reify these patterns to guide the creation of standard frameworks
 and components for the telecom domain.  I'm optimistic that the next
 generation of OO frameworks and components will be a substantial
 improvement over those we've worked with in the past.<P>
-    
+
 For more information on building reusable OO communication software
 frameworks with CORBA and ACE, see the following WWW URLs:<P>
 
-<A HREF="http://www.cs.wustl.edu/~schmidt/corba.html">http://www.cs.wustl.edu/~schmidt/corba.html</A><p>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/corba.html">http://www.dre.vanderbilt.edu/~schmidt/corba.html</A><p>
 <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE.html">http://www.dre.vanderbilt.edu/~schmidt/ACE.html.</A>
 
 <P><HR><P>
 <H3>References</H3>
 
-[Box:97] Don Box, "Understanding COM," Addison-Wesley, 
+[Box:97] Don Box, "Understanding COM," Addison-Wesley,
      Reading, MA, 1997.<P>
 
-[Brooks:75] Frederick P. Brooks, "The Mythical Man-Month," 
+[Brooks:75] Frederick P. Brooks, "The Mythical Man-Month,"
      Addison-Wesley, Reading, MA, 1975.<P>
 
 [Brooks:87] Frederick P. Brooks, "No Silver Bullet: Essence and
      Accidents of Software Engineering," IEEE Computer, Volume
      20, Number 4, April 1987, 10-19.<P>
 
-[Gosling:96] The Java Programming Language, Addison-Wesley, 
+[Gosling:96] The Java Programming Language, Addison-Wesley,
      Reading, MA, 1996.<P>
-	
+
 [Lewis:95], Ted Lewis et al., "Object Oriented Application
      Frameworks," IEEE Computer Society Press, 1995.<P>
 
@@ -266,5 +266,5 @@ Back to <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE.html">
 ACE</A> home page.<BR>
 Back to <A HREF="index.html">ACE Documentation Home</A>.
 <!--#include virtual="/~schmidt/cgi-sig.html" -->
-</BODY> 
+</BODY>
 </HTML>
diff --git a/ACE/etc/DOC-way.html b/ACE/etc/DOC-way.html
index 2b5199fdef1..2b612b283c6 100644
--- a/ACE/etc/DOC-way.html
+++ b/ACE/etc/DOC-way.html
@@ -31,7 +31,7 @@ research group:
 <LI> Value the contributions of team members
 <LI> <A HREF="http://www.cs.wustl.edu/~schmidt/research.html">Write papers</A>
 <LI> Read papers
-<LI> <A HREF="http://www.cs.wustl.edu/~schmidt/tutorials.html">Give presentations</A>
+<LI> <A HREF="http://www.dre.vanderbilt.edu/~schmidt/tutorials.html">Give presentations</A>
 <LI> Be responsive to ACE/TAO users questions and issues
 <LI> Act now, rather than later
 <LI> Accept responsibility
@@ -43,7 +43,7 @@ research group:
 <li> Watch South Park
 <li> Juggle and bounce balls
 <LI> Play ping-pong
-<LI> Swear under your breath at <A HREF="http://www.cs.wustl.edu/~schmidt/C++/">C++</A>
+<LI> Swear under your breath at <A HREF="http://www.dre.vanderbilt.edu/~schmidt/C++/">C++</A>
 <LI> Fix at least two bugs every day
 <LI> Create at least one bug every day (and then fix it ;-))
 <LI> Fix your own bugs
diff --git a/ACE/netsvcs/ACE-netsvcs.html b/ACE/netsvcs/ACE-netsvcs.html
index 7b343355b84..ddcfe3d98d3 100644
--- a/ACE/netsvcs/ACE-netsvcs.html
+++ b/ACE/netsvcs/ACE-netsvcs.html
@@ -29,7 +29,7 @@ standard library</A> of network services:<P>
 <LI><A HREF="#server-logging-overview">Server Logging Service</A>
 <LI><A HREF="#client-logging-overview">Client Logging Service</A>
 <LI><A HREF="#logging-strategy-overview">Logging Strategy Service</A>
-</UL> 
+</UL>
 </TD>
 </TABLE>
 
@@ -39,16 +39,16 @@ These services play two roles in ACE:<P>
 <LI> They provide reusable components for common distributed system
      tasks such as logging, naming, locking, and time synchronization.<P>
 <LI> They illustrate how to utilize ACE features such as the <A
-     HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#ipc">IPC
-wrappers</A>, <A HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#reactor">Reactor</A>,
-     <A HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#config">Service Configurator</A>, <A
-     HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#initialize">Service
+     HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#ipc">IPC
+wrappers</A>, <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#reactor">Reactor</A>,
+     <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#config">Service Configurator</A>, <A
+     HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#initialize">Service
 Initialization</A>, and <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#concurrency">Concurrency</A>
+HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#concurrency">Concurrency</A>
 components. <P> </UL>
 
 The heart of the ACE network services is the <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#config">Service
+HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#config">Service
 Configurator</A>, which is an object-oriented framework that automates
 the configuration and reconfiguration of multi-service daemons.  All
 the ACE network services are configured using the Service
@@ -243,8 +243,8 @@ server at port 20222 using NET_LOCAL naming context with database
 called MYDATABSE located in directory /tmp:
 
 <PRE> <CODE>
-dynamic Naming_Service Service_Object * 
-  ../lib/netsvcs:_make_ACE_Name_Acceptor() 
+dynamic Naming_Service Service_Object *
+  ../lib/netsvcs:_make_ACE_Name_Acceptor()
   "-p 20222 -c NET_LOCAL -l /tmp -s MYDATABASE"
 </PRE> </CODE>
 
@@ -253,8 +253,8 @@ client that connects to a Name Server running on host
 tango.cs.wustl.edu at port 20222:
 
 <PRE> <CODE>
-dynamic Naming_Service_Client Service_Object * 
-  ../lib/netsvcs:_make_Client_Test() 
+dynamic Naming_Service_Client Service_Object *
+  ../lib/netsvcs:_make_Client_Test()
   "-h tango.cs.wustl.edu -p 20222"
 </PRE> </CODE>
 </OL>
@@ -288,14 +288,14 @@ Time Service provides accurate, fault-tolerant clock synchronization
 for computers collaborating in local area networks and wide area
 networks.  Synchronized time services are important in distributed
 systems that require multiple hosts to maintain accurate global
-time. The architecture of the distributed time service contains the 
+time. The architecture of the distributed time service contains the
 following Time Server, Clerk, and Client components: <P>
 
 <UL>
 <LI> <I> Time Server </I> answers queries about the time made by
 Clerks. <P>
 
-<LI> <I> Clerk </I> queries one or more Time Servers to determine 
+<LI> <I> Clerk </I> queries one or more Time Servers to determine
 the correct time, calculates the approximate correct time using one of
 several distributed time algorithms and updates its own local system
 time. <P>
@@ -392,18 +392,18 @@ using the -b flag.
 server at port 20202:
 
 <PRE> <CODE>
-dynamic Time_Service Service_Object * 
-  ../lib/netsvcs:_make_ACE_TS_Server_Acceptor() 
+dynamic Time_Service Service_Object *
+  ../lib/netsvcs:_make_ACE_TS_Server_Acceptor()
   "-p 20202"
 </PRE> </CODE>
 
 <LI> Here is what a config file would look like for starting up a
 clerk that needs to connect to two servers, one at tango and one at
-lambada: 
+lambada:
 
 <PRE> <CODE>
 dynamic Time_Server_test Service_Object *
-  ../lib/netsvcs:_make_ACE_TS_Clerk_Connector () 
+  ../lib/netsvcs:_make_ACE_TS_Clerk_Connector ()
   "-h tango:20202 -h lambada:20202 -t 4"
 </PRE> </CODE>
 </OL>
@@ -461,7 +461,7 @@ synchronization primitives are listed below:<P>
        acquisition, FIFO waiter ordering, and deadlock detection.  It
        depends on the Token Server for its distributed synchronization
        semantics.<p>
-       
+
   <LI> <B><TT>ACE_Local_RLock</TT></B><P>
 
        This class implements the reader interface to canonical
@@ -500,7 +500,7 @@ synchronization primitives are listed below:<P>
        other participants (readers or writers) may hold the lock.
        ACE_Remote_RLock depends on the ACE Token Server for its
        distributed synchronization semantics.<P>
-       
+
   <LI> <B><TT>ACE_Remote_RLock</TT></B><P>
 
        This is the remote equivalent to ACE_Local_WLock.<P>
@@ -543,11 +543,11 @@ The following describes how to configure the Token Server:<P>
 
       Here is an example svc.conf entry that dynamically loads the
       Token Server specifying port number to listen on for client
-      connections:<P> 
+      connections:<P>
 
        <code><pre>
-        dynamic Token_Service Service_Object * 
-          ../lib/netsvcs:_make_ACE_Token_Acceptor() 
+        dynamic Token_Service Service_Object *
+          ../lib/netsvcs:_make_ACE_Token_Acceptor()
           "-p 10202"
        </code></pre>
        <P>
@@ -613,11 +613,11 @@ The following describes how to configure the Logging Server:<P>
 
       Here is an example svc.conf entry that dynamically loads the
       Logging Server specifying port number to listen on for client
-      connections:<P> 
+      connections:<P>
 
       <PRE> <CODE>
-      dynamic Server_Logging_Service Service_Object * 
-        ../lib/netsvcs:_make_ACE_Server_Logging_Acceptor() 
+      dynamic Server_Logging_Service Service_Object *
+        ../lib/netsvcs:_make_ACE_Server_Logging_Acceptor()
         "-p 10202"
       </PRE></CODE>
       <P>
@@ -672,7 +672,7 @@ The following describes how to configure the Logging Client:<P>
 
 Configuring a Logging Client requires specifying all or some of the
 following parameters. These parameters can be passed in to main
-through command line as follows:<P> 
+through command line as follows:<P>
 
 <TABLE cellpadding = 10 cellspacing = 0 border = 5>
 <TD VALIGN = TOP ALIGN = LEFT>
@@ -724,8 +724,8 @@ ACE_DEFAULT_RENDEZVOUS
       Logging Server: <P>
 
       <PRE> <CODE>
-      dynamic Client_Logging_Service Service_Object * 
-        ../lib/netsvcs:_make_ACE_Client_Logging_Connector() 
+      dynamic Client_Logging_Service Service_Object *
+        ../lib/netsvcs:_make_ACE_Client_Logging_Connector()
         "-h tango.cs.wustl.edu -p 10202"
       </PRE></CODE>
       <P>
@@ -761,7 +761,7 @@ default behavior is required, the Logging Strategy Service need not be
 invoked or it can be invoked with no parameters. <P>
 
 The following describes how to configure the Logging Strategy
-Service:<p> 
+Service:<p>
 
 <UL>
 <LI> <b>Startup configuration</B><P>
@@ -800,7 +800,7 @@ Strategy Service: <P>
 </TD>
 <TD VALIGN = TOP ALIGN = LEFT>
     Write messages to the ostream that gets created by specifying a
-    filename (see below) <BR> 
+    filename (see below) <BR>
 </TD>
 <TR>
 <TD VALIGN = TOP ALIGN = LEFT>
@@ -834,12 +834,12 @@ write the output to. <P>
 
 <LI> <B> Examples: </B> <P>
       Here is an example svc.conf entry that dynamically loads the
-      Logging Strategy Service specifying that the output be sent 
+      Logging Strategy Service specifying that the output be sent
       to STDERR: <P>
 
       <PRE> <CODE>
-      dynamic Logging_Strategy_Service Service_Object * 
-        ../lib/netsvcs:_make_ACE_Logging_Strategy() 
+      dynamic Logging_Strategy_Service Service_Object *
+        ../lib/netsvcs:_make_ACE_Logging_Strategy()
         "-f STDERR"
       </PRE></CODE>
       <P>
@@ -875,5 +875,5 @@ to look for the shared object files or dlls.
 Back to the <A HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE.html">
 ACE</A> home page.
 <!--#include virtual="/~schmidt/cgi-sig.html" -->
-</BODY> 
+</BODY>
 </HTML>
diff --git a/TAO/docs/configurations.html b/TAO/docs/configurations.html
index eb464678ec5..de6f52b700b 100644
--- a/TAO/docs/configurations.html
+++ b/TAO/docs/configurations.html
@@ -165,7 +165,7 @@ Roadmap</h3>
             i.e., the ORB runs in one thread and service multiple
             requests/connections simultaneously using the
             <A
-            HREF="http://www.cs.wustl.edu/~schmidt/ACE-papers.html#reactor">
+            HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-papers.html#reactor">
             ACE_Reactor</A>, which uses <tt>select</TT> or a similar
             event demultiplexing mechanism supported by the
             platform. </li> <P>