Thu Mar 20 17:05:42 1998 Michael Kircher <mk1@cs.wustl.edu>

2 files changed, 67 insertions, 0 deletions

diff --git a/TAO/ChangeLog-98c b/TAO/ChangeLog-98c
index c33423e5093..3233845b1f9 100644
--- a/TAO/ChangeLog-98c
+++ b/TAO/ChangeLog-98c
@@ -1,3 +1,8 @@
+Thu Mar 20 17:05:42 1998  Michael Kircher  <mk1@cs.wustl.edu>
+
+        * $TAO_ROOT/docs/releasenotes/index.html:
+          Documentation about the DOVE demo
+
 Fri Mar 20 16:21:28 1998  Irfan Pyarali  <irfan@cs.wustl.edu>
 
 	* tests/POA/Generic_Servant/MyFooServant.h: No need to include
diff --git a/TAO/docs/releasenotes/index.html b/TAO/docs/releasenotes/index.html
index ee9ec381688..9a77787876f 100644
--- a/TAO/docs/releasenotes/index.html
+++ b/TAO/docs/releasenotes/index.html
@@ -572,7 +572,69 @@ Notice that these procedures only setup the IDL compiler to perform correctly.
 <P>p.s. If anyone knows how to set a default setting in VC so we don't
 need to perform these procedures every time a new project gets set up,
 please let us know. Thanks.
+<P>
 
+<HR>
+<H3>
+<A NAME="DOVE demo"></A>Latest news about the DOVE demo</H3>
+Point of contact: <A HREF="mailto:mk1@cec.wustl.edu">Michael Kircher</A>.
+<P>
+DOVE is described in detail on the following site:
+<A HREF="http://www.cs.wustl.edu/~schmidt/dove.html">DOVE documentation</A>
+<P>
+We focus on the following goals at the moment:
+<LI>
+Have a DOVE Browser running using Java Beans as vizualization components
+<LI>
+Have the Event Channel as DOVE Agent running with an Event Consumer
+in the DOVE Browser.
+<LI>
+Having a MIB which dumps all events transfered on the Event Channel
+into a file on persistent storage for later reuse. (Not implemented yet)
+</LI>
+<P>
+Two demos are available right now: 
+<LI>
+One using a fixed set of visualization components and the 
+Event Channel as DOVE Agent.
+<LI>
+A new demo using independent visualization components (Java Beans)
+and the Event Channel as DOVE Agent. Connections can be established
+between monitored metrics and the visualization components.
+</LI>
+<P>
+In the concept of the new demo we have three major components: 
+Observables (monitored metrics), Observers (a Java Bean
+for displaying the metric) and a DataHandler (for demultiplexing the 
+monitored metrics to the appropriate Observables).
+Each component inherits from a base class, so that a certain behavior
+of the components can be assured for each component. Relationships
+between components are based on these base classes.
+<P>
+The used Java Beans are required to conform to some standards, as
+they have to support a function called "getProperty" which allows
+the DOVE Browser to determine if the vizualization capabilities of 
+a specific Java Bean are sufficient to display the metric.
+A JavaBean is for example a Java Panel which shows a Graph of
+the delivered doubles. So all metrics can be displayed by this visualization 
+component which can be expressed by a single double.
+<P>
+The DataHandler is connected to the Event Push Consumer (PUSH, because
+we use the push concept of the Event Service). The Event Push Consumer
+does not know what kind of data is transported. The only component 
+knowing all the details about the dependencies of the metrics is
+the DataHandler. This separation allows easy extension and change
+of the demo.
+<P>
+<A HREF="http://students.cec.wustl.edu/~mk1/dove.html">Object Diagrams</A>
+are available about this new concept.
+<P>
+Major milestones are:
+<LI>
+Having the DOVE demo properly running on NT
+<LI>
+Add MIB functionality
+</LI>
 <P>
 <HR>