summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authormarina <marina@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-10-20 00:13:35 +0000
committermarina <marina@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-10-20 00:13:35 +0000
commit17ff91ed2a2035e6f1fe16de4153bc7415682687 (patch)
tree5d1351126b53f40d478f385381191bf3311649a2
parentd5b1a5b4a18db77094c532c6e078c3aaf75346db (diff)
downloadATCD-17ff91ed2a2035e6f1fe16de4153bc7415682687.tar.gz
Added to the current status of RT CORBA section.
-rw-r--r--TAO/docs/releasenotes/index.html11
1 files changed, 11 insertions, 0 deletions
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index e8995714a9f..0cbd9cb87f6 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -734,6 +734,17 @@ currently supported are <CODE>SYNC_NONE</CODE> and
<li> Buffering Constraint Policy is completely supported by TAO
providing flexible levels of flushing and queueing in the ORB. </li>
+<li> ClientPriorityPolicy has been implemented. This TAO-specific
+policy allows clients to specify priority to be used as a
+selection criteria in choosing server endpoints for carrying out
+consequent corba requests on objects. This client-side feature
+together with the server-side capability to create multiple endpoints with
+different priorities directly contributes to maintaining end-to-end
+priority in a distributed system. Please see TAO/tao/TAO.idl for
+ClientPriorityPolicy interface, and TAO/tests/Endpoint_Per_Priority for
+its use. Current implementation does not work properly in presence of
+location forward messages.
+
</ul>
Known issues:
<ul>