diff options
author | pradeep <pradeep@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2000-03-15 15:51:43 +0000 |
---|---|---|
committer | pradeep <pradeep@ae88bc3d-4319-0410-8dbf-d08b4c9d3795> | 2000-03-15 15:51:43 +0000 |
commit | 7e7f5e499a409480320393dcbd32f2bf8032e79b (patch) | |
tree | 9be4fa901756ef928c5e9ccbda2d6ffdeaa42011 | |
parent | 418476a6cbce73bb8a2b6d518a04455096f05fd3 (diff) | |
download | ATCD-7e7f5e499a409480320393dcbd32f2bf8032e79b.tar.gz |
*** empty log message ***
-rw-r--r-- | TAO/orbsvcs/examples/Notify/README | 18 | ||||
-rw-r--r-- | TAO/orbsvcs/examples/Notify/Subscribe/README | 28 |
2 files changed, 46 insertions, 0 deletions
diff --git a/TAO/orbsvcs/examples/Notify/README b/TAO/orbsvcs/examples/Notify/README new file mode 100644 index 00000000000..7028c60fe5d --- /dev/null +++ b/TAO/orbsvcs/examples/Notify/README @@ -0,0 +1,18 @@ + +Notification Service examples: + +This directory has examples to illustrate how to use the Notification Service + +Examples: + +Filter: A simple example to how how to do filtering of events. +------ +An event passing through the channel encounters filters at the proxy, +admin and channel level.This example shows how to setup filters and use them. + +Subscribe: A simple example to show how to specify subscription constraints. +--------- +This example does not add any filters to keep the example simple. +If filters are added, then they would be evaluated *after* the event type +constraints have been met. +Thus subscriptions are a way of provide coarse grain filtering. diff --git a/TAO/orbsvcs/examples/Notify/Subscribe/README b/TAO/orbsvcs/examples/Notify/Subscribe/README new file mode 100644 index 00000000000..8dc7fac8cb6 --- /dev/null +++ b/TAO/orbsvcs/examples/Notify/Subscribe/README @@ -0,0 +1,28 @@ +Subscribe example: +---------------- +Note: This example is under construction. + +The Notification service must be up and running before launching this example. +(See the README under $TAO_ROOT/orbsvcs/Notify_Service for more details.) + +Description: +------------ +This example sets subscription event type constraints (domain_name,type_name): + +At the consumer admin. C1 = ("domain_A", "Type_1"). +This means that all consumers connected to this admin object are interested +in receiving events of "domain_A" and "Type_1". + +At consumer 1, C2 = ("domain_B", Type_2") +At consumer 2, C3 = ("domain_C", Type_3") + +A supplier then send events of all 3 types to the event channel. +i,e. event E1 with event type C1, + event E2 with event type C2 and + event E3 with event type C3. + +From the subscriptions, consumer1 receives E1 and E2, (not E3) and +consumer2 receives E1 and E3 (not E2). + +running the ./Subscribe example will output the events received by each +consumer.
\ No newline at end of file |