summaryrefslogtreecommitdiff
path: root/TAO/DevGuideExamples/NotifyService/QoSProperties/README
blob: d35c31067461dbcf83942b287a4b4a0ab98e0e23 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
// $Id$

Event Notification Service


File: DevGuideExamples/NotifyService/QoSProperties/README


This example extends the NotifyService/Messenger example by
demonstrating how QoS features can be incorporated into the utilization 
of the Notification channel.

The Client code is stored in:

DevGuideExamples/NotifyService/QoSProperties/MessengerClient.cpp

The Server code is stored in:

DevGuideExamples/NotifyService/QoSProperties/MessengerServer.cpp

The Consumer code is stored in:

DevGuideExamples/NotifyService/QoSProperties/MessengerConsumer.cpp


How to Run
----------

To start the Naming Service:
----------------------------
$TAO_ROOT/orbsvcs/Naming_Service/Naming_Service -o ns.ior&

To start the Notification Service:
---------------------------------
$TAO_ROOT/orbsvcs/Notify_Service/Notify_Service -ORBInitRef NameService=file://ns.ior&

To start the server/supplier
----------------------------
./MessengerServer -ORBInitRef NameService=file://ns.ior

To start the consumer
---------------------
./MessengerConsumer -ORBInitRef NameService=file://ns.ior

To start the client
-------------------
./MessengerClient -ORBInitRef NameService=file://ns.ior



Exeuction via Perl Script
-------------------------

A Perl script has been created to automate the steps shown
above.  This script can be run via the following command:

./run_test.pl