ChangeLogTag:Fri Jun 18 11:47:22 2004 Balachandran Natarajan <bala@dre.vanderbilt.edu>

7 files changed, 60 insertions, 89 deletions

diff --git a/docs/ACE-SSL.html b/docs/ACE-SSL.html
index 58ea01f7851..b3ba856bbc5 100644
--- a/docs/ACE-SSL.html
+++ b/docs/ACE-SSL.html
@@ -29,12 +29,6 @@
       but hopefully through using the ACE+SSL interface your questions
       will be reduced.</p> 
 
-    <H3>What is the status of ACE+SSL</H3>
-    <p>ACE+SSL is currently still in early development. If forced to
-      name names, we would call the core functionality beta, while the
-      interface and niceties are still in an alpha stage of
-      development.</p> 
-
     <H3>How do I get ACE+SSL?</H3>
     <p>Due to the relaxation of export restrictions we have gained
       permission to distribute ACE+SSL along with the normal ACE
diff --git a/docs/ACE-bug-process.html b/docs/ACE-bug-process.html
index b9f276657bc..f28c2ded7ce 100644
--- a/docs/ACE-bug-process.html
+++ b/docs/ACE-bug-process.html
@@ -7,10 +7,10 @@
 <HR>
 <H3>ACE+TAO Bug Fixing Policies</H3>
 
-As <A HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</A> and <A
-HREF="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</A> have grown in
-popularity the volume of mail on the <A
-HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">ACE+TAO users
+As <A HREF="http://www.dre.vanderbilt.edu/ACE">ACE</A>,and <A
+HREF="http://www.dre.vanderbilt.edu/TAO">TAO</A> have grown in
+popularity the volume of mail on the
+<A HREF="http://www.cs.wustl.edu/~schmidt/ACE-mail.html">ACE+TAO users  
 mailing list</A> and USENET newsgroup <A
 HREF="news:comp.soft-sys.ace">comp.soft-sys.ace</A> has grown
 considerably.  While this increase is healthy, and a natural
@@ -19,8 +19,8 @@ the resources of the DOC <A
 HREF="http://www.cs.wustl.edu/~schmidt/ACE-members.html">research
 group</A> at <A
 HREF="http://www.cs.wustl.edu/~schmidt/doc-center.html">Washington
-University</A> and <A
-HREF="http://www.cs.wustl.edu/~schmidt/doc-lab.html">UC Irvine</A> to
+University</A>, <A HREF="http://zen.uci.edu">UC Irvine</A> and <A
+HREF="http://www.dre.vanderbilt.edu"> ISIS</A> to
 respond to all the traffic immediately.  Moreover, our prompt bug
 fixes may actually be discouraging the creation of a larger community
 of users who have deep knowledge of how ACE and TAO work and can help
diff --git a/docs/ACE-development-process.html b/docs/ACE-development-process.html
index 2a6ba473820..8a67701ed7c 100644
--- a/docs/ACE-development-process.html
+++ b/docs/ACE-development-process.html
@@ -35,9 +35,9 @@ blocked for the duration of the broken build, the fix, and the
 rebuild.<p>
 
 <hr>
-<h3>The ACE+TAO Development Process</h3>
+<h3>The ACE+TAO+CIAO Development Process</h3>
 
-The ACE+TAO development process looks like:<p>
+The ACE+TAO+CIAO development process looks like:<p>
 <ol>
   <li>Every change to ACE+TAO must have a bug report.  <em>Change</em>
     includes fixes, enhancements, updates, and so on.
@@ -127,33 +127,34 @@ violator.  This is also intentional, desirable, beneficial, and the
 Right Thing[TM] to do.<p>
 
 <p><hr>
-<H3>The ACE+TAO Release Process</H3>
+<H3>The ACE+TAO+CIAO Release Process</H3>
 <P>
 
-Minor releases of ACE+TAO occur periodically, typically twice a year.
-Minor releases have two-digit numbers, <EM>e.g.,</EM> 5.3.  Major
-releases are released infrequently, typically once a year.  Major
-releases are 1-digit numbers, <EM>e.g.,</EM>5, that include
+Minor releases of ACE+TAO+CIAO occur periodically, typically twice a
+year. Minor releases have two-digit numbers, <EM>e.g.,</EM> 5.3.
+Major releases are released infrequently, typically once a year.
+Major releases are 1-digit numbers, <EM>e.g.,</EM>5, that include 
 substantially new functionality.  Both major and minor releases are
 carefully tested on all platforms the ACE+TAO run on.  In particular,
-we do not put out major or minor releases of ACE+TAO until all the
+we do not put out major or minor releases of ACE+TAO+CIAO until all the
 compilations and regression tests work successful on all the platform
 we support. <P>
 
 Between major/minor releases, we release betas periodically,
-<EM>e.g.,</EM> once a month, so that ACE+TAO users can download and
-test our latest work in progress.  ACE+TAO beta kits have three-digit
-numbers, <EM>e.g.,</EM> 5.3.1.  Betas are often not as stable as the
-major or minor releases, but they often contain important fixes that
-aren't in the official releases.  Although we try to ensure the
-quality of betas, they may not compile cleanly on all platforms, nor
-will they necessarily pass all of the tests on all platforms.  They
-will, however, compile cleanly and pass most tests on most platforms.
-As usual, we endeavor to fix any problems that arise as quickly as
-possible.  Naturally, if you require 100% predictable stability and
-support, please contact one of the companies that provides <A
+<EM>e.g.,</EM> once a month, so that ACE+TAO+CIAO users can download
+and test our latest work in progress.  ACE+TAO+CIAO beta kits have
+three-digit  numbers, <EM>e.g.,</EM> 5.3.1.  Betas are often not as
+stable as the major or minor releases, but they often contain
+important fixes that aren't in the official releases.  Although we try
+to ensure the quality of betas, they may not compile cleanly on all
+platforms, nor will they necessarily pass all of the tests on all
+platforms.  They will, however, compile cleanly and pass most tests on
+most platforms. As usual, we endeavor to fix any problems that arise
+as quickly as possible.  Naturally, if you require 100% predictable
+stability and support, please contact one of the companies that
+provides <A
 HREF="http://www.cs.wustl.edu/~schmidt/commercial-support.html">
-commercial support</A> for ACE+TAO.<P>
+commercial support</A> for ACE+TAO.<P> 
 
 The first beta following a major/minor release is called a
 <EM>bug-fix-only</EM> (BFO) beta. As the name implies this beta will
diff --git a/docs/ACE-guidelines.html b/docs/ACE-guidelines.html
index 0b56983ba2e..486ab50300e 100644
--- a/docs/ACE-guidelines.html
+++ b/docs/ACE-guidelines.html
@@ -44,8 +44,8 @@ bgcolor="#ffffff">
 
 	<li>Try to avoid creating files with exceesively long names (45 characters).
         Moreover, ensure that the names of generated files eg. MakeProjectCreator,
-        tao_idl do not also go beoynd that limit. Some operating systems cannot
-        handle very long file names correctly.<p>
+        tao_idl do not also go beyond that limit. Some operating
+        systems cannot handle very long file names correctly.<p>
 
     <li>If you add a comment to code that is directed to, or
         requires the attention of, a particular individual:
@@ -121,7 +121,7 @@ bgcolor="#ffffff">
         minimizes footprint, and reduces the likelihood of interference
         when other interfaces need to be added later.  (See the
         <a href="#ACE_Time_Value example">ACE_Time_Value example</a>
-        below.<p>
+        .<p>
 
   </ul>
 
diff --git a/docs/ACE-porting.html b/docs/ACE-porting.html
index 95f58c11845..24421d943d4 100644
--- a/docs/ACE-porting.html
+++ b/docs/ACE-porting.html
@@ -13,9 +13,9 @@
 
 <HR><P> <H3>Porting ACE, TAO, and CIAO to a New OS Platform</H3><P>
 
-<A HREF="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</A>, <A
-HREF="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</A>, and <A
-HREF="http://www.cs.wustl.edu/~schmidt/CIAO.html">CIAO</A> have been
+<A HREF="http://www.dre.vanderbilt.edu/ACE">ACE</A>, <A
+HREF="http://www.dre.vanderbilt.edu/TAO">TAO</A>, and <A
+HREF="http://www.dre.vanderbilt.edu/CIAO">CIAO</A> have been
 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
@@ -141,18 +141,20 @@ order to compile ACE and TAO:
 
 <UL>
 <LI> <B>Templates</B> -- The C++ compiler must support templates.
-    However, it need not support template member functions nor must it
-    support template traits. <P>
+    However, it need not support template member functions and of
+    the advanced concepts outlined in <A
+    HREF="http://www.moderncppdesign.com/"> Modern C++ Design</A>. <P>
 
 <LI> <B>Multiple inheritance and dynamic binding</B> -- The C++
     compiler must support multiple inheritance and dynamic
     binding. <P>
 
-<LI> <B>Namespaces</B> -- ACE utilizes C++ namespaces, so the C++ compiler
-    must support them.<P>
+<LI> <B>Namespaces</B> -- ACE+TAO+CIAO utilizes C++ namespaces, so the
+    C++ compiler must support them.<P>
 
-<LI> <B>ANSI casts and RTTI</B> -- ACE uses the new ANSI C++ casts, so the C++ compiler
-    must support them, which implies support for RTTI.<P>
+<LI> <B>ANSI casts and RTTI</B> -- ACE+TAO+CIAO uses the ANSI C++
+    casts, so the C++ compiler  must support them, which implies
+    support for RTTI.<P> 
 
 </UL>
 
diff --git a/docs/msvc_notes.txt b/docs/msvc_notes.txt
index db20825d8ee..a0965a3e8bc 100644
--- a/docs/msvc_notes.txt
+++ b/docs/msvc_notes.txt
@@ -7,12 +7,14 @@ polished as other ACE documentation.
 
 @subsection msvc_configurations Configurations
 
-MSVC project files come with several configurations.  The main two are Debug
-and Release.  Debug produces libraries and executables with debugging symbols
-and doesn't enable inlining.  The Release configuration enables optimizations
-and leaves out debugging symbols.  All projects (with the exception of some
-of the tests) contain both configurations.  Most of the libraries also contain
-four more, Static Release/Debug and MFC Release/Debug.
+MSVC workspace and solution files come with several configurations.  The
+main two are Debug and Release.  Debug produces libraries and
+executables with debugging symbols and doesn't enable inlining.  The
+Release configuration enables optimizations and leaves out debugging
+symbols.  All projects contain both configurations. If you want to
+build static or mfc versions of th elibrary you need to use different
+project and solution files. Project files with _Static extension
+denote workspaces for building static libraries.
 
 Different configurations produce different libraries and executables.  For
 example, Debug versions of dynamic libraries are always named *d.dll (like 
@@ -22,7 +24,7 @@ executables are usually placed in the Release subdirectory.  Other common
 suffixes include *sd.lib for Static Debug and *s.lib for Static Release.
 
 Projects only use the same configuration versions of the libraries.  The Debug
-version of an ACE example only uses 
+version of an ACE example only uses debug version of ACE library.
 
 @subsection msvc_otheroptions How to Set Other Options
 
@@ -45,48 +47,19 @@ ACE libraries are:
 - ace
 - ACE_RMCast
 - ACE_SSL
+- ACE_TMCast
 
 And for TAO we have the main TAO library and several sub libraries which
 contain extra features of TAO that aren't always needed (such as the POA
 in TAO_PortableServer).
 
-- TAO
-- TAO_DynamicAny
-- TAO_DynamicInterface
-- TAO_IORManip
-- TAO_IORTable
-- TAO_PortableServer
-- TAO_SmartProxies
-- TAO_Strategies
-
 And finally we have the orbsvcs libraries.  Each ORB service is contained
 in its own library.  More libraries may be needed to be linked in, since
 some services require the use of others (such as TAO_AV requiring 
 TAO_CosTrading and TAO_CosProperty).  
 
-- TAO_AV
-- TAO_CosConcurrency
-- TAO_CosEvent
-- TAO_CosLifeCycle
-- TAO_CosNaming
-- TAO_CosNotification
-- TAO_CosProperty
-- TAO_CosTime
-- TAO_CosTrading
-- TAO_DsLogAdmin
-- TAO_Fault_Tolerance
-- TAO_LoadBalancing
-- TAO_RTEvent
-- TAO_RTOLDEvent
-- TAO_RTSched
-- TAO_RTSchedEvent
-- TAO_Security
-- TAO_SSLIOP
-- TAO_Svc_Utils
-
-The *.lib files are located in the directory where the project that creates
-them exists.  The *.dll files are usually placed in ACE_wrappers\bin (so you
-only need to add one directory to your path).  
+The *.lib and *.dll files are located in ACE_wrappers/lib.  You need
+to point your PATH to $ACE_ROOT/lib for running the applications. 
 
 I hesitate to put down explicit instructions on what libraries need to be
 linked in, considering that the libraries are being split apart more and more
diff --git a/docs/usage-bugzilla.html b/docs/usage-bugzilla.html
index 66971f7e1de..8d0e1a0d342 100644
--- a/docs/usage-bugzilla.html
+++ b/docs/usage-bugzilla.html
@@ -10,7 +10,7 @@
 
     <p>
       The
-      <a href="http://www.cs.wustl.edu/~schmidt/doc-center.html">
+      <a href="http://www.dre.vanderbilt.edu">
 	Center for Distributed Object Computing</a> uses the
       <a href="http://www.mozilla.org/projects/bugzilla/">Bugzilla</a>
       bug tracking system to keep track of existing problems and
@@ -20,8 +20,9 @@
       To streamline our development process, you can now use it to
       enter problem reports or make a request for a particular feature
       that you'd like to see integrated into
-      <a href="http://www.cs.wustl.edu/~schmidt/ACE.html">ACE</a> or
-      <a href="http://www.cs.wustl.edu/~schmidt/TAO.html">TAO</a>.
+      <a href="http://www.dre.vanderbilt.edu/ACE">ACE</a>, 
+      <a href="http://www.dre.vanderbilt.edu/TAO">TAO</a> or <a
+      href="http://www.dre.vanderbilt.edu/CIAO">CIAO</a>.
 
     <p>
       You can also use it to track the status of a particular bug or
@@ -32,8 +33,8 @@
     <p>
       The bug tracking system is located at the following web site:
       <samp>
-	<a href="http://deuce.doc.wustl.edu/bugzilla/">
-	  http://deuce.doc.wustl.edu/bugzilla/
+	<a href="http://deuce.doc.wustl.edu/bugzilla/index.cgi">
+	  http://deuce.doc.wustl.edu/bugzilla/index.cgi
 	</a>
       </samp>
 
@@ -90,7 +91,7 @@
 
 
     <hr>
-    <address><a href="mailto:othman@cs.wustl.edu">Ossama Othman</a></address>
+    <address><a href="mailto:ossama@dre.vanderbilt.edu">Ossama Othman</a></address>
 <!-- Created: Wed Aug 18 14:45:31 EDT 1999 -->
 <!-- hhmts start -->
 Last modified: Wed Nov 14 21:36:32 Pacific Standard Time 2001