summaryrefslogtreecommitdiff
path: root/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README')
-rw-r--r--TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README8
1 files changed, 4 insertions, 4 deletions
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
index 4a60c213d06..0a31c28f632 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/EventSequence/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
Event Notification Service
@@ -7,12 +7,12 @@ File: examples/NotifyService/EventSequence/README
This directory contains an example which transmits an EventBatch using the Notification Service.
-This example extends the Messenger example in GettingStarted directory
-to illustrate how the Notification channel can be used to push event batches
+This example extends the Messenger example in GettingStarted directory
+to illustrate how the Notification channel can be used to push event batches
from the supplier to the consumer. The example uses the push/push model.
The MessengerServer in this example plays the role of a server for
-the MessengerClient and the role of a supplier for the MessengerConsumer.
+the MessengerClient and the role of a supplier for the MessengerConsumer.
The flow of messages is shown below:
MessengerClient->MessengerSupplier->NotificationChannel->MessengerConsumer.