summaryrefslogtreecommitdiff
path: root/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README')
-rw-r--r--TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README b/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
index 29688714703..c060e8ae5ba 100644
--- a/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
+++ b/TAO/orbsvcs/DevGuideExamples/NotifyService/Messenger/README
@@ -1,4 +1,4 @@
-// $Id$
+$Id$
Event Notification Service
@@ -7,13 +7,13 @@ File: examples/NotifyService/Messenger/README
This directory contains a simple example of using the Notification Service.
-This example extends the Messenger example in GettingStarted directory
+This example extends the Messenger example in GettingStarted directory
to illustrate how the Notification channel can be used to push messages
from the supplier to the consumer. Structured events are used to demonstrate
the operation of the channel. 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.