Updated several broken links

23 files changed, 78 insertions, 95 deletions

diff --git a/ACE/ACE-INSTALL.html b/ACE/ACE-INSTALL.html
index 23f45159384..cf053e11321 100644
--- a/ACE/ACE-INSTALL.html
+++ b/ACE/ACE-INSTALL.html
@@ -231,19 +231,19 @@ over the years, ACE's success has greatly increased the amount of
 effort required to keep up with its maintenance, answer users'
 questions, and give design guidance. Riverace offers world-class
 commercial services to support ACE users.  OCI, PrismTech, and Remedy
-offer similar services for TAO, allowing the DOC group's primary focus
+offer similar services for ACE and TAO, allowing the DOC group's primary focus
 to shift back to their main goal: <em>research</em>. The DOC group is
 fundamentally focused on (and <a
-href="http://www.cs.wustl.edu/%7Eschmidt/resume-grants.html">funded
+href="http://www.dre.vanderbilt.edu/~schmidt/resume-grants.html">funded
 by</a>) advanced R&amp;D projects. The group continues to be
 intimately involved in ACE+TAO development and maintenance, but with
 revised priorities for maintenance. The <a
 href="docs/ACE-bug-process.html">bug
 fixing policies</a> followed by the DOC group are designed to strike a
 balance between their many <a
-href="http://www.cs.wustl.edu/%7Eschmidt/research.html">research
+href="http://www.dre.vanderbilt.edu/~schmidt/research.html">research
 projects</a> and their commitment to the ACE+TAO <a
-href="http://www.cs.wustl.edu/%7Eschmidt/ACE-users.html">user
+href="http://www.dre.vanderbilt.edu/~schmidt/ACE-users.html">user
 community</a>.  Naturally, we will be happy to accept well-tested
 patches from the ACE+TAO user community for any platforms that aren't
 supported by the DOC group, Riverace, OCI or Remedy IT. </p><p>
@@ -3129,7 +3129,7 @@ quickly.
 
 <hr><p>
 
-Back to the <a href="http://www.cs.wustl.edu/%7Eschmidt/ACE.html">ACE</a>
+Back to the <a href="https://www.dre.vanderbilt.edu/~schmidt/ACE.html">ACE</a>
 home page.
 
 
diff --git a/ACE/Kokyu/docs/Kokyu.html b/ACE/Kokyu/docs/Kokyu.html
index b476a849a85..fb1b0905e3a 100644
--- a/ACE/Kokyu/docs/Kokyu.html
+++ b/ACE/Kokyu/docs/Kokyu.html
@@ -31,7 +31,7 @@ Real-time CORBA (DSRTCORBA) schedulers</a>
 Kokyu is a portable middleware scheduling framework designed to provide
 flexible scheduling and dispatching services within the context of higher-level
 middleware. Kokyu currently provides real-time scheduling and dispatching
-services for TAO’s real-time CORBA Event Service, which mediates supplier-consumer
+services for TAO�s real-time CORBA Event Service, which mediates supplier-consumer
 relationships between application operations. Kokyu consists primarily
 of two cooperating infrastructure segments, illustrated in Figure 1:
 <center>
@@ -54,7 +54,7 @@ are ordered, by assigning priority levels and rates to tasks, and producing
 a configuration specification for the dispatching mechanism. The dispatcher
 is responsible for enforcing the ordering of operation dispatches using
 different threads, requests queues, and timers configured according to
-the scheduler’s specification. The combined framework provides an implicit
+the scheduler�s specification. The combined framework provides an implicit
 projection of scheduling heuristics into appropriate dispatching infrastructure
 configurations, so that the scheduling and dispatching infrastructure segments
 can be optimized both separately and in combination.
@@ -72,7 +72,7 @@ within a fixed CORBA IDL interface, thereby enabling different strategies
 to be configured independently from applications that use them.
 <h3>
 <a NAME="FlexDispatch"></a>Flexible Dispatching Framework</h3>
-The right side of Figure 1 shows the essential features of Kokyu’s flexible
+The right side of Figure 1 shows the essential features of Kokyu�s flexible
 task dispatching infrastructure. Key features of the dispatching infrastructure
 that are essential to performing our optimizations are as follows:
 <p><b>Dispatching queues:</b> Each task is assigned by our strategized
@@ -96,16 +96,16 @@ the highest is at the head of the queue at the point when one is to be
 dequeued. We consider three disciplines:
 <ul>
 <li>
-Static – Tasks are ordered by a static subpriority value – results in FIFO
+Static � Tasks are ordered by a static subpriority value � results in FIFO
 ordering if all static subpriorities are made the same; static queues at
 different priority levels can be used to implement an RMS scheduling strategy.</li>
 
 <li>
-Deadline – Tasks are ordered by time to deadline; a single deadline queue
+Deadline � Tasks are ordered by time to deadline; a single deadline queue
 can be used to implement the earliest deadline first (EDF) scheduling strategy.</li>
 
 <li>
-Laxity – Tasks are ordered by slack time, or laxity – the time to deadline
+Laxity � Tasks are ordered by slack time, or laxity � the time to deadline
 minus the execution time; a single laxity queue can be used to implement
 the minimum laxity first (MLF) scheduling strategy; laxity queues at different
 priority levels can be used to implement the maximum urgency first (MUF)
@@ -125,7 +125,7 @@ in the Kokyu dispatching framework.
 the Kokyu scheduling framework is used to configure and operate a dispatching
 module. During system initialization, each dispatching module obtains the
 thread priority and dispatching type for each of its queues, typically
-from the scheduling service’s output interface. Next, each queue is assigned
+from the scheduling service�s output interface. Next, each queue is assigned
 a unique dispatching priority number, a unique thread priority, and an
 enumerated dispatching type. Finally, each dispatching module has an ordered
 queue of pending dispatches per dispatching priority. To preserve QoS guarantees,
@@ -140,18 +140,18 @@ the dispatching type:
 <ul>
 <li>
 <b>STATIC DISPATCHING</b>: This type specifies a queue that only considers
-the static portion of an operation’s dispatching subpriority.</li>
+the static portion of an operation�s dispatching subpriority.</li>
 
 <li>
 <b>DEADLINE DISPATCHING</b>: This type specifies a queue that considers
-the dynamic and static portions of an operation’s dispatching subpriority,
+the dynamic and static portions of an operation�s dispatching subpriority,
 and updates the dynamic portion according to the time remaining until the
-operation’s deadline.</li>
+operation�s deadline.</li>
 
 <li>
 <b>LAXITY DISPATCHING</b>: This type specifies a queue that considers the
-dynamic and static portions of an operation’s dispatching subpriority,
-and updates the dynamic portion according to the operation’s laxity.</li>
+dynamic and static portions of an operation�s dispatching subpriority,
+and updates the dynamic portion according to the operation�s laxity.</li>
 </ul>
 
 <h3>
@@ -406,7 +406,7 @@ special issue on Real-Time Middleware, guest editor Wei Zhao, March 2001,
 Vol. 20 No. 2</li>
 
 <li>
-Christopher D. Gill, Douglas C. Schmidt, and Ron Cytron, <a href="http://www.cs.wustl.edu/~schmidt/PDF/embedded_sched.pdf">Multi-Paradigm
+Christopher D. Gill, Douglas C. Schmidt, and Ron Cytron, <a href="http://www.dre.vanderbilt.edu/~schmidt/PDF/embedded_sched.pdf">Multi-Paradigm
 Scheduling for Distributed Real-Time Embedded Computing</a>, IEEE Proceedings
 Special Issue on Modeling and Design of Embedded Systems, Volume 91, Number
 1, January 2003.</li>
diff --git a/ACE/ace/WIN32_Proactor.h b/ACE/ace/WIN32_Proactor.h
index 1625fa8ce1c..e370ee08ddc 100644
--- a/ACE/ace/WIN32_Proactor.h
+++ b/ACE/ace/WIN32_Proactor.h
@@ -44,7 +44,7 @@ class ACE_WIN32_Proactor_Timer_Handler;
  * @brief A manager for asynchronous event demultiplexing on Win32.
  *
  * See the Proactor pattern description at
- * http://www.cs.wustl.edu/~schmidt/PDF/proactor.pdf for more
+ * http://www.dre.vanderbilt.edu/~schmidt/PDF/proactor.pdf for more
  * details.
  */
 class ACE_Export ACE_WIN32_Proactor : public ACE_Proactor_Impl
diff --git a/ACE/apps/Gateway/README b/ACE/apps/Gateway/README
index 7fe06ead493..8831425cff5 100644
--- a/ACE/apps/Gateway/README
+++ b/ACE/apps/Gateway/README
@@ -12,7 +12,7 @@ distributed system.
 You can get a paper that explains the patterns used in this
 implementation at the following WWW URL:
 
-http://www.cs.wustl.edu/~schmidt/PDF/TAPOS-00.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/TAPOS-00.pdf
 
 ----------------------------------------
 
diff --git a/ACE/docs/ACE-guidelines.html b/ACE/docs/ACE-guidelines.html
index 4989e60ad00..d95affef956 100644
--- a/ACE/docs/ACE-guidelines.html
+++ b/ACE/docs/ACE-guidelines.html
@@ -991,7 +991,7 @@ Foo::bar ()
 </ul>
 
 <hr>
-<h3><a href="http://www.cs.wustl.edu/~schmidt/ACE-overview.html">ACE</a>
+<h3><a href="http://www.dre.vanderbilt.edu/~schmidt/ACE-overview.html">ACE</a>
   Shared Libary Guidelines</h3>
     <ul>
       <li>
@@ -1113,7 +1113,7 @@ public:
 
 
 <hr>
-<h3><a href="http://www.cs.wustl.edu/~schmidt/ACE-overview.html">ACE</a>
+<h3><a href="http://www.dre.vanderbilt.edu/~schmidt/ACE-overview.html">ACE</a>
   Usage Guidelines</h3>
 <ul>
   <li>Always use the <strong><code>ACE_OS</code></strong>
@@ -1247,33 +1247,16 @@ public:
 
 
 <hr>
-<h3><a href="http://www.cs.wustl.edu/~schmidt/ACE-overview.html">Other
+<h3><a href="http://www.dre.vanderbilt.edu/~schmidt/ACE-overview.html">Other
   ACE</a> and
-  <a href="http://www.cs.wustl.edu/~schmidt/TAO-overview.html">TAO</a>
+  <a href="http://www.dre.vanderbilt.edu/~schmidt/TAO-overview.html">TAO</a>
   Guidelines</h3>
 <ul>
   <li>When enhancing, updating, or fixing ACE or TAO, always:
   <ol>
-    <li>Test your change on at least Windows and Linux before commiting.
-      After commiting watch the scoreboard to catch errors your change
+    <li>Test your change on at least Windows and Linux before committing.
+      After committing watch the scoreboard to catch errors your change
       may be related to on other platforms.
-    <li>Add an entry to the appropriate ChangeLog.  TAO and some
-      ACE subdirectories, such as <a href="../ASNMP">ASNMP</a>,
-      <a href="../apps/JAWS">JAWS</a>, and
-      <a href="../apps/gperf">gperf,</a> have their
-      own ChangeLogs.  If you don't use one of those, use the
-      <a href="../ChangeLog">ChangeLog</a> in the top-level
-      <a href="..">ACE_wrappers</a> directory. A ChangeLog entry should
-      have the form:
-      <pre>&lt;tab&gt; * dir/file.ext [(methods)]: description...</pre>
-      If you have a number of files, the names should be on separate lines.
-      In this case, it's also ok to start the description on a new line
-      indented to "dir."
-    <li>Commit your change using a message of this form:<p>
-<code>
-ChangeLogTag: Thu Jul 22 09:55:10 UTC 1999  David L. Levine
- &lt;levine@cs.wustl.edu&gt;
-</code>
     <li>If the change is in response to a request by someone else:
     <ol>
       <li>Make sure that person is acknowledged in
@@ -1292,11 +1275,11 @@ ChangeLogTag: Thu Jul 22 09:55:10 UTC 1999  David L. Levine
 
 
 <hr>
-<h3>SVN Usage Guidelines</h3>
+<h3>Git Usage Guidelines</h3>
 <ul>
   <li>Always make sure that a change builds and executes correctly
-    on at least one platform before checking it into the SVN repository.
-    All changes <strong>must</strong> be tested with g++ before commiting.
+    on at least one platform before checking it into the git repository.
+    All changes <strong>must</strong> be tested with g++ before committing.
     That means you may need to test on at least two platforms.<p>
 </ul>
 
diff --git a/ACE/docs/ACE-porting.html b/ACE/docs/ACE-porting.html
index 400f5452135..6b8af33b1e2 100644
--- a/ACE/docs/ACE-porting.html
+++ b/ACE/docs/ACE-porting.html
@@ -20,7 +20,7 @@ ported to <A HREF="http://www.dre.vanderbilt.edu/versions.html">many
 OS platforms</A>.  Porting ACE, TAO, and CIAO to new platforms is
 fairly easy.  The following document describes the step-by-step
 process to use when porting the various <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-overview.html">components
+HREF="http://www.dre.vanderbilt.edu/~schmidt/ACE-overview.html">components
 and layers</A> in ACE to a new OS platform.  Once ACE is ported, it is
 straightforward to port TAO and CIAO, as well.<P>
 
diff --git a/ACE/docs/index.html b/ACE/docs/index.html
index fac33571284..5250e652e07 100644
--- a/ACE/docs/index.html
+++ b/ACE/docs/index.html
@@ -45,7 +45,7 @@ ask. <P>
 <ul>
   <li><a href="http://www.dre.vanderbilt.edu/ACE-papers.html">Technical Papers</a> -
       Postscript versions of many ACE papers.
-  <li>Tutorial on C++ Network Programming with Patterns, Frameworks, and ACE<a href="http://www.cs.wustl.edu/~schmidt/PDF/ACE-tutorial.pdf">[pdf]</a>
+  <li>Tutorial on C++ Network Programming with Patterns, Frameworks, and ACE<a href="http://www.dre.vanderbilt.edu/~schmidt/PDF/ACE-tutorial.pdf">[pdf]</a>
       <a href="http://www.cs.wustl.edu/~schmidt/ACE-tutorial.ps.gz">[ps.gz]</a>
     <!-- Bob's original can always be found at: http://dox.netwrench.com/acedox/fmm/ -->
   <li><a href="ACE-FMM.html">ACE FMM</a> - ACE &quot;Frequently Made Mistakes&quot;
diff --git a/ACE/examples/ASX/Event_Server/README b/ACE/examples/ASX/Event_Server/README
index 435f7fc2094..0e9b5fc909f 100644
--- a/ACE/examples/ASX/Event_Server/README
+++ b/ACE/examples/ASX/Event_Server/README
@@ -3,11 +3,11 @@
 This subdirectory illustrates a number of the ACE ASX framework
 features using an ACE_Stream application called the Event Server.  For
 more information on the design and use of the ACE ASX framework please
-see http://www.cs.wustl.edu/~schmidt/PDF/C++-USENIX-94.pdf and
-http://www.cs.wustl.edu/~schmidt/PDF/ACE-concurrency.pdf.  For more
+see http://www.dre.vanderbilt.edu/~schmidt/PDF/C++-USENIX-94.pdf and
+http://www.dre.vanderbilt.edu/~schmidt/PDF/ACE-concurrency.pdf.  For more
 information on the Event Server, please see
 
-http://www.cs.wustl.edu/~schmidt/PDF/DSEJ-94.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/DSEJ-94.pdf
 
 The Event Server example works as follows:
 
diff --git a/ACE/examples/Service_Configurator/IPC-tests/README b/ACE/examples/Service_Configurator/IPC-tests/README
index ffb4c11eb00..d76602e0ad5 100644
--- a/ACE/examples/Service_Configurator/IPC-tests/README
+++ b/ACE/examples/Service_Configurator/IPC-tests/README
@@ -10,11 +10,11 @@ Wrapper Facade, Reactor, and Component Configurator patterns in POSA2
 <http://www.dre.vanderbilt.edu/~schmidt/POSA/> and check out the following
 papers on the ACE framework components:
 
-http://www.cs.wustl.edu/~schmidt/PDF/IPC_SAP-92.pdf
-http://www.cs.wustl.edu/~schmidt/PDF/Reactor1-93.pdf
-http://www.cs.wustl.edu/~schmidt/PDF/Reactor2-93.pdf
-http://www.cs.wustl.edu/~schmidt/PDF/reactor-rules.pdf
-http://www.cs.wustl.edu/~schmidt/PDF/Svc-Conf.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/IPC_SAP-92.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/Reactor1-93.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/Reactor2-93.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/reactor-rules.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/Svc-Conf.pdf
 
 The key to running these client/server tests is to understand the
 purpose of the svc.conf file located in the
diff --git a/ACE/tests/Future_Set_Test.cpp b/ACE/tests/Future_Set_Test.cpp
index 8611fdd87c0..c8c6e1617b0 100644
--- a/ACE/tests/Future_Set_Test.cpp
+++ b/ACE/tests/Future_Set_Test.cpp
@@ -5,7 +5,7 @@
  *
  *  This example tests the ACE Future Set and illustrates an
  *  implementation of the Active Object pattern, which is available
- *  at <http://www.cs.wustl.edu/~schmidt/PDF/Act-Obj.pdf>.  The
+ *  at <http://www.dre.vanderbilt.edu/~schmidt/PDF/Act-Obj.pdf>.  The
  *  Active Object itself is very simple -- it determines if numbers
  *  are prime.
  *
diff --git a/ACE/tests/Refcounted_Auto_Ptr_Test.cpp b/ACE/tests/Refcounted_Auto_Ptr_Test.cpp
index 6cff912cfa5..0609e204cfd 100644
--- a/ACE/tests/Refcounted_Auto_Ptr_Test.cpp
+++ b/ACE/tests/Refcounted_Auto_Ptr_Test.cpp
@@ -5,7 +5,7 @@
  *  This example tests the <ACE_Refcounted_Auto_Ptr> and illustrates
  *  how they may be dispersed between multiple threads using an
  *  implementation of the Active Object pattern, which is available
- *  at <http://www.cs.wustl.edu/~schmidt/PDF/Act-Obj.pdf>.
+ *  at <http://www.dre.vanderbilt.edu/~schmidt/PDF/Act-Obj.pdf>.
  *
  *  @author Johnny Tucker <johnny_tucker@yahoo.com>
  */
diff --git a/TAO/docs/Smart_Proxies.html b/TAO/docs/Smart_Proxies.html
index 405ab601fda..7cef472cb74 100644
--- a/TAO/docs/Smart_Proxies.html
+++ b/TAO/docs/Smart_Proxies.html
@@ -20,7 +20,7 @@ interface. A proxy packages the request which gets marshalled and
 sent to the target object.  A paper that describes TAO's <A
 HREF="interceptors.html">portable interceptor</A> and smart proxy
 support is available <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/smart_proxies.pdf">online</A>.</p></p>
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/smart_proxies.pdf">online</A>.</p></p>
 
 <Hr><P>
 <h3><a name="toc">Table of Contents</a></h3>
@@ -392,7 +392,7 @@ and so for all object instances the same kind of proxy is used.  On
 disabling this default option one can achieve the use of different
 smart proxies for every object instead of every interface.
 For details please see the paper on
-<a href="http://www.cs.wustl.edu/~schmidt/PDF/COOTS-00.pdf">
+<a href="http://www.dre.vanderbilt.edu/~schmidt/PDF/COOTS-00.pdf">
 Meta-programming Mechanisms for ORB Middleware as well as the test at
 $TAO_ROOT/tests/Smart_Proxies/Policy.
 
diff --git a/TAO/docs/TAO-metrics.html b/TAO/docs/TAO-metrics.html
index 857f888e642..f172ada15b4 100644
--- a/TAO/docs/TAO-metrics.html
+++ b/TAO/docs/TAO-metrics.html
@@ -20,14 +20,14 @@ benchmarking of TAO.
 
 <OL>
 <LI> <A
-    HREF="http://www.cs.wustl.edu/~schmidt/PDF/RT-OS.pdf">TAO's
+    HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/RT-OS.pdf">TAO's
     performance on different real-time operating systems</A>
 <LI> <A
-    HREF="http://www.cs.wustl.edu/~schmidt/PDF/words-02.pdf">More real-time operating system performance measurements for TAO</A>
+    HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/words-02.pdf">More real-time operating system performance measurements for TAO</A>
 <LI> <A HREF="http://cs.wustl.edu/~schmidt/PDF/COOTS-99.pdf">TAO's Demultiplexing Latency</A>
-<LI> <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/JSAC-99.pdf">TAO's IIOP performance</A>
-<LI> <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/ami2.pdf">TAO's AMI performance</A>
-<LI> <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/pluggable_protocols.pdf">TAO's
+<LI> <A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/JSAC-99.pdf">TAO's IIOP performance</A>
+<LI> <A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/ami2.pdf">TAO's AMI performance</A>
+<LI> <A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/pluggable_protocols.pdf">TAO's
     pluggable protocols performance</A>
 <LI> <A HREF="../../docs/ACE-subsets.html">Subsetting of ACE and minimum TAO</A>
 <LI> Current and past performance and footprint metrics are available
diff --git a/TAO/docs/compiler.html b/TAO/docs/compiler.html
index f87debfae0c..c12076ec35c 100644
--- a/TAO/docs/compiler.html
+++ b/TAO/docs/compiler.html
@@ -22,7 +22,7 @@ online CORBA specification</A> and the <A
 HREF="http://www.triodia.com/staff/michi-henning.html">Advanced CORBA
 Programming with C++</A> book.  More information on the design of
 TAO's IDL compiler is also available <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/ami1.pdf">online</A>.
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/ami1.pdf">online</A>.
 Finally, comprehensive documentation on TAO's IDL compiler is
 available in the OCI <A HREF="http://www.theaceorb.com/product/index.html">TAO
 Developer's Guide</A>.<P>
@@ -177,7 +177,7 @@ incoming operation with the correct operation at the servant.  TAO's
 IDL compiler supports perfect hashing, binary search, and dynamic
 hashing demuxing strategies.  By default, TAO's IDL compiler tries to
 generate perfect hash functions, which is generally the most <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/COOTS-99.pdf">efficient and
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/COOTS-99.pdf">efficient and
 predictable operation demuxing technique</A>.  To generate perfect
 hash functions, TAO's IDL compiler uses <a
 href="http://www.dre.vanderbilt.edu/~schmidt/PDF/gperf.pdf">gperf </a>, which
@@ -231,7 +231,7 @@ generate the right collocated stubs (or not generating any at all using
 both  '<a href="#Sp"><code>-Sp</code></a>' and '<a
 href="#Sd"><code>-Sd</code></a>' flags at the same time if
 it's a pure client.)  See our <a
-href="http://www.cs.wustl.edu/~schmidt/PDF/C++-report-col18.pdf">collocation
+href="http://www.dre.vanderbilt.edu/~schmidt/PDF/C++-report-col18.pdf">collocation
 paper</a> for a detail discussion on the collocation support in
 TAO.<p>
 
diff --git a/TAO/docs/configurations.html b/TAO/docs/configurations.html
index 5f02fbbb689..eb464678ec5 100644
--- a/TAO/docs/configurations.html
+++ b/TAO/docs/configurations.html
@@ -21,11 +21,11 @@ documentation, various components in TAO can be customized by
 specifying options for those components.  This document illustrates
 how to combine these options to affect the behavior and performance of
 a TAO ORB, particularly its <a
-href="http://www.cs.wustl.edu/~schmidt/PDF/CACM-arch.pdf">concurrency
+href="http://www.dre.vanderbilt.edu/~schmidt/PDF/CACM-arch.pdf">concurrency
 model</a>.  </p>
 
 <p> TAO configures itself using the <a
-href="http://www.cs.wustl.edu/~schmidt/PDF/Svc-Conf.pdf">ACE Service
+href="http://www.dre.vanderbilt.edu/~schmidt/PDF/Svc-Conf.pdf">ACE Service
 Configurator</a> framework.  Options are therefore specified using the
 <tt>svc.conf</tt> file (if you want to use a different file name, use
 the <tt><a href="Options.html#svcfonf">-ORBSvcConf</a></tt> option).
diff --git a/TAO/docs/interceptors.html b/TAO/docs/interceptors.html
index f7dc262c4aa..0adf1e3cf3a 100644
--- a/TAO/docs/interceptors.html
+++ b/TAO/docs/interceptors.html
@@ -19,7 +19,7 @@ old interceptors will no longer be supported now that we have the new
 mechanism in place.  A paper that describes TAO's portable
 interceptors and <A HREF="Smart_Proxies.html">smart proxies</A> is
 available
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/smart_proxies.pdf">online</A>.
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/smart_proxies.pdf">online</A>.
 </p>
 
 <hr><P>
@@ -74,7 +74,7 @@ object.</p>
 <p>
 Details of this implementation along with benchmarking is available in
 the paper on <a
-href="http://www.cs.wustl.edu/~schmidt/PDF/COOTS-00.pdf">Meta-programming
+href="http://www.dre.vanderbilt.edu/~schmidt/PDF/COOTS-00.pdf">Meta-programming
 mechanisms.</a>
 </p>
 
diff --git a/TAO/docs/pluggable_protocols/index.html b/TAO/docs/pluggable_protocols/index.html
index a5bf23320a1..c07c18a8217 100644
--- a/TAO/docs/pluggable_protocols/index.html
+++ b/TAO/docs/pluggable_protocols/index.html
@@ -59,9 +59,9 @@ links that describe TAO's pluggable protocols framework, though not
 how to implement one: <BLOCKQUOTE> <A
 HREF="../releasenotes/index.html#pp">../releasenotes/index.html#pp</A><BR>
 
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/PfHSN.pdf">http://www.cs.wustl.edu/~schmidt/PDF/PfHSN.pdf</A><BR>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/PfHSN.pdf">http://www.dre.vanderbilt.edu/~schmidt/PDF/PfHSN.pdf</A><BR>
 <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/pluggable_protocols.pdf">http://www.cs.wustl.edu/~schmidt/PDF/pluggable_protocols.pdf</A>
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/pluggable_protocols.pdf">http://www.dre.vanderbilt.edu/~schmidt/PDF/pluggable_protocols.pdf</A>
 </BLOCKQUOTE>
 
 <P>
@@ -2559,38 +2559,38 @@ were:
 <BLOCKQUOTE>
 Reactor (
 <A HREF="http://www.cs.wustl.edu/~schmidt/Reactor.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/Reactor.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/Reactor.pdf">PDF</A>
 )<BR>
 
 Reactor1-93 (
 <A HREF="http://www.cs.wustl.edu/~schmidt/Reactor1-93.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/Reactor1-93.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/Reactor1-93.pdf">PDF</A>
 )<BR>
 
 Reactor2-93 (
 <A HREF="http://www.cs.wustl.edu/~schmidt/Reactor2-93.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/Reactor2-93.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/Reactor2-93.pdf">PDF</A>
 )<BR>
 
 reactor-rules (
 <A HREF="http://www.cs.wustl.edu/~schmidt/reactor-rules.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/reactor-rules.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/reactor-rules.pdf">PDF</A>
 )<BR>
 
 reactor-siemens (
 <A HREF="http://www.cs.wustl.edu/~schmidt/reactor-siemens.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/reactor-siemens.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/reactor-siemens.pdf">PDF</A>
 )<BR>
 
 Svc-Conf (
 <A
 HREF="http://www.cs.wustl.edu/~schmidt/Svc-Conf.ps.gz">PostScript</A> |
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/Svc-Conf.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/Svc-Conf.pdf">PDF</A>
 )<BR>
 
 Acc-Con (
 <A HREF="http://www.cs.wustl.edu/~schmidt/Acc-Con.ps.gz">PostScript</A>
-<A HREF="http://www.cs.wustl.edu/~schmidt/PDF/Acc-Con.pdf">PDF</A>
+<A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/Acc-Con.pdf">PDF</A>
 )
 </BLOCKQUOTE>
 <P>These are all readily available from the TAO and ACE website.
@@ -2917,7 +2917,7 @@ Bibliography</A>
 </H3><DL COMPACT><DD><P></P><DT><A NAME="Schmidt:97c">1</A>
 <DD>
 D. C. Schmidt,
-``<A HREF=http://www.cs.wustl.edu/~schmidt/PDF/Acc-Con.pdf>
+``<A HREF=http://www.dre.vanderbilt.edu/~schmidt/PDF/Acc-Con.pdf>
   Acceptor and Connector: Design Patterns for Initializing
   Communication Services</A>,''
   in <EM> Pattern Languages of Program Design</EM>
@@ -2927,7 +2927,7 @@ D. C. Schmidt,
 <P></P><DT><A NAME="Schmidt:97e">2</A>
 <DD>
 C. Cleeland, D. C. Schmidt and T. Harrison,
-``<A HREF=http://www.cs.wustl.edu/~schmidt/PDF/External-Polymorphism.pdf>
+``<A HREF=http://www.dre.vanderbilt.edu/~schmidt/PDF/External-Polymorphism.pdf>
   External Polymorphism -- An Object Structural Pattern for
   Transparently Extending Concrete Data Types</A>,''
   in <EM> Pattern Languages of Program Design</EM>
@@ -2937,7 +2937,7 @@ C. Cleeland, D. C. Schmidt and T. Harrison,
 <P></P><DT><A NAME="Schmidt:94k">3</A>
 <DD>
 D. C. Schmidt and T. Suda,
-  ``<A HREF=http://www.cs.wustl.edu/~schmidt/PDF/DSEJ-94.pdf>
+  ``<A HREF=http://www.dre.vanderbilt.edu/~schmidt/PDF/DSEJ-94.pdf>
   An Object-Oriented Framework for Dynamically
   Configuring Extensible Distributed Communication Systems</A>,'' <EM> IEE/BCS
   Distributed Systems Engineering Journal (Special Issue on Configurable
@@ -2959,7 +2959,7 @@ Architecture - A System of Patterns</EM>.</A> Wiley and Sons, 1996.
 <DD>
 Carlos O'Ryan, Fred Kuhns, Douglas C. Schmidt, Ossama Othman, and Jeff
 Parsons, <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/pluggable_protocols.pdf"> The
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/pluggable_protocols.pdf"> The
 Design and Performance of a Pluggable Protocols Framework for
 Real-time Distributed Object Computing Middleware</A>, Proceedings of
 the IFIP/ACM <A
@@ -2968,7 +2968,7 @@ Conference, Pallisades, New York, April 3-7, 2000. <P>
 
 <P></P><DT><A NAME="Schmidt:99c">7</A> <DD> Fred Kuhns, Carlos O'Ryan,
 Douglas C. Schmidt, Ossama Othman, and Jeff Parsons, <A
-HREF="http://www.cs.wustl.edu/~schmidt/PDF/PfHSN.pdf">The Design and
+HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/PfHSN.pdf">The Design and
 Performance of a Pluggable Protocols Framework for Object Request
 Broker Middleware,</A> Proceedings of the <A
 HREF="http://www.isi.edu/pfhsn99/call.html">IFIP Sixth International
diff --git a/TAO/docs/releasenotes/amh.html b/TAO/docs/releasenotes/amh.html
index 556692c3d16..1989df3b73c 100644
--- a/TAO/docs/releasenotes/amh.html
+++ b/TAO/docs/releasenotes/amh.html
@@ -32,7 +32,7 @@ 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>
+<a href="http://www.dre.vanderbilt.edu/~schmidt/PDF/AMH.pdf">AMH-Motivation. </a>
 
 <HR SIZE=4 WIDTH="100%">
 
@@ -45,7 +45,7 @@ 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
-<a href="http://www.cs.wustl.edu/~schmidt/PDF/DOA-02.pdf"">AMH-In-Detail. </a>
+<a href="http://www.dre.vanderbilt.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
diff --git a/TAO/docs/releasenotes/ftcorba_services.html b/TAO/docs/releasenotes/ftcorba_services.html
index f4854e1bfd5..d603acd716a 100644
--- a/TAO/docs/releasenotes/ftcorba_services.html
+++ b/TAO/docs/releasenotes/ftcorba_services.html
@@ -78,7 +78,7 @@ project included:
 <ol>
   <li>Adding a <code>SEMI_ACTIVE</code> replication style similar to
   that described <a
-    href="http://www.cs.wustl.edu/~schmidt/PDF/WDMS02.pdf">here</a>.</li>
+    href="http://www.dre.vanderbilt.edu/~schmidt/PDF/WDMS02.pdf">here</a>.</li>
   <li>Separating interfaces and type definitions that are common
   across multiple specifications into a Portable Group module as
   described in the <a
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index f676bdf3c39..6ddcae06f14 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -1972,7 +1972,7 @@ Point of contact: <a href="mailto:ossama@dre.vanderbilt.edu">Ossama Othman</a>
 <h4>
 Current Status:</h4>
 TAO's
-<a href="http://www.cs.wustl.edu/~schmidt/PDF/load_balancing.pdf">Load
+<a href="http://www.dre.vanderbilt.edu/~schmidt/PDF/load_balancing.pdf">Load
 Balancer</a> currently implements the latest revision of the OMG <i>Load
 Balancing and Monitoring</i> proposed specification.
 <p>It provides many features and advantages over the previous prototype.
diff --git a/TAO/docs/tutorials/Quoter/index.html b/TAO/docs/tutorials/Quoter/index.html
index 2de4e419112..9e4b4110b4e 100644
--- a/TAO/docs/tutorials/Quoter/index.html
+++ b/TAO/docs/tutorials/Quoter/index.html
@@ -29,9 +29,9 @@
       applications to explore advanced TAO features, such as
       <A HREF="http://www.cs.wustl.edu/~schmidt/report-doc.html#ami">
         asynchronous method invocation</A>,
-      <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/C++-report-col19.pdf">
+      <A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/C++-report-col19.pdf">
         reliable oneways</A>,
-      the <A HREF="http://www.cs.wustl.edu/~schmidt/PDF/JSAC-98.pdf">
+      the <A HREF="http://www.dre.vanderbilt.edu/~schmidt/PDF/JSAC-98.pdf">
         real-time Events Service</A>,
       the <A HREF="../../INS.html">
         Interoperable Naming Service</A>
diff --git a/TAO/performance-tests/Cubit/TAO/MT_Cubit/README b/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
index b90030606ef..35ab6b1afe0 100644
--- a/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
+++ b/TAO/performance-tests/Cubit/TAO/MT_Cubit/README
@@ -10,8 +10,8 @@ utilization, and degree of priority inversion incurred by TAO twoway
 operations invoked under different workloads and priorities.  For
 more information and empirical results, please see
 
-http://www.cs.wustl.edu/~schmidt/PDF/RT-perf.pdf
-http://www.cs.wustl.edu/~schmidt/PDF/RT-OS.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/RT-perf.pdf
+http://www.dre.vanderbilt.edu/~schmidt/PDF/RT-OS.pdf
 
 COMPILING
 ---------
diff --git a/TAO/tests/Smart_Proxies/Policy/README b/TAO/tests/Smart_Proxies/Policy/README
index 7f464d09f25..05f9243cf73 100644
--- a/TAO/tests/Smart_Proxies/Policy/README
+++ b/TAO/tests/Smart_Proxies/Policy/README
@@ -84,4 +84,4 @@ While in send portion of the output, the smart proxy is used only once, that is
 first time around and the default proxy is called upon the second time.  This is because
 the smart proxy factory gets unregistered since the "one-shot" policy is disabled.
 
-For details, please see: http://www.cs.wustl.edu/~schmidt/PDF/COOTS-00.pdf
+For details, please see: http://www.dre.vanderbilt.edu/~schmidt/PDF/COOTS-00.pdf