summaryrefslogtreecommitdiff
path: root/TAO/examples/OBV/Typed_Events/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/examples/OBV/Typed_Events/README')
-rw-r--r--TAO/examples/OBV/Typed_Events/README31
1 files changed, 0 insertions, 31 deletions
diff --git a/TAO/examples/OBV/Typed_Events/README b/TAO/examples/OBV/Typed_Events/README
deleted file mode 100644
index 77b3950e13f..00000000000
--- a/TAO/examples/OBV/Typed_Events/README
+++ /dev/null
@@ -1,31 +0,0 @@
-// $Id$
-
-Typed Events
-============
-
-This is a demonstration of the CORBA 2.3 valuetype feature.
-Event_Types.idl defines a hierarchy of event classes. The common
-attributes (indeed not CORBA attributes, they're state members)
-like creation time and id of the origin are in a base class.
-Concrete events like Temperature, Position and Log Message are derived
-from this class.
-
-The client sends a few random events to the server. The server has
-suitable implementations of the event classes. So it is able to
-show the incoming events by invoking the do_print () operation, which is
-declared in the Event baseclass.
-After that the server does an "alarm" check on the event.
-For each possible origin id (KITCHEN, BATHROOM) a criterion has been
-registered. The criterion which equals the origin id of the event is
-searched and then asked with is_critical (event).
-
-Finally a list with all the events which causes an alarm is
-requested by the client.
-
-
-Start with:
-
-% ./server -o ior
-% ./client -f ior [-x]
-
-