summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorpradeep <pradeep@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-01-14 02:06:59 +0000
committerpradeep <pradeep@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>1999-01-14 02:06:59 +0000
commita63dcacfc04ea7ece3a5308d2e91cf045c1443eb (patch)
tree5e47452ad8150f438fef3911847110cfd124a926
parentcf1ad198a3c2d610f8ff6658b37a629a7d2566a8 (diff)
downloadATCD-a63dcacfc04ea7ece3a5308d2e91cf045c1443eb.tar.gz
*** empty log message ***
-rw-r--r--TAO/docs/releasenotes/index.html33
1 files changed, 17 insertions, 16 deletions
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index 2cb73a012ff..565881b0162 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -517,19 +517,22 @@ algorithm can be used in the future.</li>
<li>
Implementation of the Timer Event Service.</li>
</ul>
-For OMG's documentation on the Time Service please read&nbsp; <a href="ftp://ftp.omg.org/pub/docs/formal/97-02-22.pdf">The
-Time Service Specification.</a>
+For OMG's documentation on the Time Service please read&nbsp; <a href="ftp://ftp.omg.org/pub/docs/formal/97-12-11.pdf">The
+Time Service Specification. (.pdf) </a>
+<a href="ftp://ftp.omg.org/pub/docs/formal/97-12-11.pdf"> (.ps) </a>
<p>
<hr WIDTH="100%">
<h3>
<a NAME="ec"></a>CORBA Event Service</h3>
<h4>
-<!-- @@ Pradeep: can you find an URL that points to the OMG website? --><!-- IMHO it will look more official like that. -->Last
-Updated: Sat Jan&nbsp; 2 01:17:33 CST 1999</h4>
+Last updated: Wed Jan 13 20:01:27 CST 1999
+</h4>
Point of contact: <a href="mailto:pradeep@cs.wustl.edu">Pradeep Gore</a>
-<p>The COS compliant Event Service implements the <a href="http://siesta.cs.wustl.edu/~coryan/Docs/formal/97-12-11.pdf">Event
-Service Specification</a>
+<p>The COS compliant Event Service implements the Event Service Specification:
+<a href="http://www.omg.org/docs/formal/97-12-11.pdf">(.pdf)</a>,
+<a href="http://www.omg.org/docs/formal/97-12-11.ps">(.ps)</a>
+
<br>This implementation is based on the Real Time Event service.
<h3>
Features in this release:</h3>
@@ -538,10 +541,15 @@ Features in this release:</h3>
<li>
The Event Channel (<tt>$TAO_ROOT/orbsvcs/orbsvcs/CosEvent</tt>) supports
the <tt>push </tt>style event communication.</li>
-
+<br>
<li>
A simple test (<tt>$TAO_ROOT/orbsvcs/tests/CosEC_Basic</tt>) demonstrates
how to create and use the event channel.</li>
+<br>
+<li>
+Event Service (<tt>$TAO_ROOT/orbsvcs/CosEvent_Service</tt>)The Event Service
+creates a COS compliant event channel and registers it with the naming service with the default name "CosEventChannel".
+ <br>Please read the associated README for more details.
</ul>
<h3>
@@ -549,17 +557,10 @@ Current Work:</h3>
<ul>
<li>
-<tt>Event Service</tt>: The Event Service will create an event channel
-and register it with the naming service, Push style consumers and producers</li>
-
-<br>can then connect to the service and send /receive events.
-<li>
-<tt>CosEC_Multiple</tt>:&nbsp; This test demonstrates how multiple CosEC's
-connect to one RtEC and how multiple consumers and producers exchange events
-in this configuration.</li>
+CosEC_Multiple: <tt>($TAO_ROOT/orbsvcs/tests/CosEC_Multiple)</tt>:&nbsp; This test demonstrates how multiple CosEC's connect to one RtEC and how multiple consumers and producers exchange events in this configuration.</li>
</ul>
-<hr><!--#include virtual="ec.html" -->
+<!--#include virtual="ec.html" -->
<p>
<hr>
<h3>