summaryrefslogtreecommitdiff
path: root/TAO/docs
diff options
context:
space:
mode:
authornanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-06-16 06:33:54 +0000
committernanbor <nanbor@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-06-16 06:33:54 +0000
commit3e73ab25906053af515e361aa7266a13ddc70e79 (patch)
treec34118541913ea7078017d92d8f79e3529f068e6 /TAO/docs
parent24a3747b099702dcc1e135f603486a333b30f9d5 (diff)
downloadATCD-3e73ab25906053af515e361aa7266a13ddc70e79.tar.gz
docs
Diffstat (limited to 'TAO/docs')
-rw-r--r--TAO/docs/compiler.html6
-rw-r--r--TAO/docs/poa_migration.html5
-rw-r--r--TAO/docs/releasenotes/orbcore.html23
3 files changed, 10 insertions, 24 deletions
diff --git a/TAO/docs/compiler.html b/TAO/docs/compiler.html
index c0bcd8ac235..2f2872de23f 100644
--- a/TAO/docs/compiler.html
+++ b/TAO/docs/compiler.html
@@ -43,12 +43,6 @@ you only need to <CODE>#include</CODE> the client stubs declared in
the <tt>C.h</tt> file and the skeletons in the <tt>S.h</tt> file in
your code. <P>
-To transparently support collocated objects, clients and servers
-should both link with the object files for the stubs and skeletons.
-If your clients are ``pure'', <EM>i.e.</EM>, they don't need
-collocation, you can give an option to the IDL compiler to avoid
-linking clients with the skeletons. <P>
-
<HR><P>
<h3>
Operation Demuxing Strategies</h3>
diff --git a/TAO/docs/poa_migration.html b/TAO/docs/poa_migration.html
index 9c925e511f2..bcb446b1d4d 100644
--- a/TAO/docs/poa_migration.html
+++ b/TAO/docs/poa_migration.html
@@ -2,6 +2,7 @@
<HEAD>
<META NAME="GENERATOR" CONTENT="Adobe PageMill 2.0 Mac">
<TITLE>Migrating from the BOA to the POA</TITLE>
+ <!-- $Id$ -->
</HEAD>
<BODY text = "#000000"
@@ -34,9 +35,7 @@ HREF="http://www.iona.com/hyplan/vinoski/">Steve Vinoski</a>.
<H4><a name="Client-side Changes">Client-side Changes</a></h4>
<ul>
-<li>Very little has changed. Thus, many applications require to changes.</li><P>
-<li>You'll have to insure that the Makefile includes .o's for both the server
-and client, which is necessary in TAO to support collocation.</li> <P>
+<li>Very little has changed. Thus, many applications require no changes.</li><P>
</ul>
<h4><a name="Server-side Changes">Server-side Changes</a></h4>
diff --git a/TAO/docs/releasenotes/orbcore.html b/TAO/docs/releasenotes/orbcore.html
index 71acfa21988..adc0794d2a0 100644
--- a/TAO/docs/releasenotes/orbcore.html
+++ b/TAO/docs/releasenotes/orbcore.html
@@ -52,21 +52,6 @@ Point of contact: <a href="mailto: irfan@cs.wustl.edu">Irfan Pyarali</a>
<a name="issues"><h3>Known issues:</h3></a>
<ul>
- <li><p>Since collocated objects run in the client thread's context,
- calling <code>CORBA::ORB::shutdown()</code> does <em>not</em>
- actually close down the target ORB but instead on the client
- side ORB. This issue will be addressed in the new ORB Core
- architecture.</p>
-
- <p>Also, since the collocated invocations circumvent POA
- completely, POA Current won't get set up, LOCATION_FORWARD will
- not work, race condition may occur when several threads invoke
- operations on an objects registered with POAs with SINGLE_THREAD
- policy, operation invocations will still get thru even the POA
- is in holding state, or invoking operations on a servant that
- has already been deactivated.</p>
- </li>
-
<li><p>When using the thread-per-connection concurrency model, if
some client leave the socket connection open without sending any
request, the server will crash on NT. This is because we are
@@ -437,6 +422,14 @@ new ORB Core structure.
</p>
</li>
+ <li><p>Added CORBA compliant collocated stubs implementation. The new
+ implementation now query POA for permission to proceed thus fixed
+ many potentially subtle problems. The original collocation implementation
+ is still supported using by specifying the -ORBCollocationStrategy direct
+ command option (because the original scheme has slightly less method
+ invocation overhead.)
+ </li>
+
</ul>
<!-- --------------------- -->
<a href="#toc">Back to TOC</a>