diff options
Diffstat (limited to 'TAO')
| -rw-r--r-- | TAO/orbsvcs/CosEvent_Service/README | 8 | ||||
| -rw-r--r-- | TAO/orbsvcs/DevGuideExamples/PortableInterceptors/PICurrent_NameService/README | 8 | ||||
| -rw-r--r-- | TAO/orbsvcs/Notify_Service/README | 2 | ||||
| -rw-r--r-- | TAO/orbsvcs/TAO_Service/README | 20 |
4 files changed, 20 insertions, 18 deletions
diff --git a/TAO/orbsvcs/CosEvent_Service/README b/TAO/orbsvcs/CosEvent_Service/README index 448f3d47dda..19c004cfe45 100644 --- a/TAO/orbsvcs/CosEvent_Service/README +++ b/TAO/orbsvcs/CosEvent_Service/README @@ -1,3 +1,5 @@ +$Id$ + CORBA COS Event Service ----------------------- @@ -82,10 +84,10 @@ $TAO_ROOT/docs/cec_options.html Note: ==== - By default, the Naming Service disables multicast discovery. + By default, the Naming Service disables multicast discovery. The "-m 1" option enables the Naming Service to be resolved via - multicast. - + multicast. + If you do not wish to do this, then use the -ORBInitRef option in which case the Naming Service should be started as: diff --git a/TAO/orbsvcs/DevGuideExamples/PortableInterceptors/PICurrent_NameService/README b/TAO/orbsvcs/DevGuideExamples/PortableInterceptors/PICurrent_NameService/README index bce171848f2..05f86c5e86f 100644 --- a/TAO/orbsvcs/DevGuideExamples/PortableInterceptors/PICurrent_NameService/README +++ b/TAO/orbsvcs/DevGuideExamples/PortableInterceptors/PICurrent_NameService/README @@ -7,14 +7,14 @@ File: DevGuideExamples/PortableInterceptor/PICurrent_NameService/README This directory contains an example that shows how the PICurrent can -be used to stop client-side interceptor recursions. This example is +be used to stop client-side interceptor recursions. This example is identical to the ../PICurrent example but uses the Naming Service. -This example is based on the Messenger example in GettingStarted -directory. A message is send by MessengerClient and displayed by +This example is based on the Messenger example in GettingStarted +directory. A message is send by MessengerClient and displayed by MessengerServer. When the client receives a reply, it asks the server for the current time. This causes a recursive call at the receive_reply() -interception point. A flag is passed in the PICurrent to let the client +interception point. A flag is passed in the PICurrent to let the client know the call is recursive. How to Run diff --git a/TAO/orbsvcs/Notify_Service/README b/TAO/orbsvcs/Notify_Service/README index bf5387008f2..595b87edcaf 100644 --- a/TAO/orbsvcs/Notify_Service/README +++ b/TAO/orbsvcs/Notify_Service/README @@ -70,7 +70,7 @@ Command line arguments: Notify_Service, which is on by default. "-LoggingInterval seconds" : Sets up a logging interval timer for the ORB's - reactor. This is required to use the ACE + reactor. This is required to use the ACE Logging Service features such as file sizing and rotation. See the example below. diff --git a/TAO/orbsvcs/TAO_Service/README b/TAO/orbsvcs/TAO_Service/README index 799c4d1cb2f..a07867626b7 100644 --- a/TAO/orbsvcs/TAO_Service/README +++ b/TAO/orbsvcs/TAO_Service/README @@ -1,7 +1,7 @@ // $Id$ -This directory has a generic server which opens and reads the svc.conf file in -the directory and dynamically loads and unloads the various ORB services as per +This directory has a generic server which opens and reads the svc.conf file in +the directory and dynamically loads and unloads the various ORB services as per the entries made in the svc.conf file. To Load a Service Dynamically: @@ -9,12 +9,12 @@ To Load a Service Dynamically: 1. Add an entry to the svc.conf which specifies the service name that you wish to load dynamically. - + The syntax for loading a service dynamically is: dynamic < Service name i.e. name that you want the Service Repository to use to identify the dynamically linked Service_Object - so that you can look it up later via, + so that you can look it up later via, e.g., ACE_Dynamic_Service::instance () > \ < The type of the service > \ < The shared DLL that has the function @@ -25,7 +25,7 @@ To Load a Service Dynamically: To load Naming Service dynamically : ---------------------------------- - + dynamic TAO_Naming_Loader Service_Object * \ TAO_CosNaming_Serv:_make_TAO_Naming_Loader () "dummy -o ns.ior" @@ -36,7 +36,7 @@ To load Naming Service dynamically : To load Event Service dynamically: --------------------------------- - + In the case of Event Service, we also want to load the default Event Service Factory in addition to the Event Service. So, we need to add these two entries when we want to load the event service. @@ -59,7 +59,7 @@ dynamic TAO_Trading_Loader Service_Object * \ To Remove a Service ******************* - The directive for removing a service is <remove>. Removing a + The directive for removing a service is <remove>. Removing a service is simpler. Add the following entry to the same svc.conf file after commenting the entry for loading the same service, so that the service is not loaded again. @@ -92,9 +92,9 @@ To Run TAO_Service : 1. Start with a empty svc.conf file. Run the TAO_Service. Make sure that you start with an empty svc.conf file because the ORB_init () and -the service configurator get pretty confused. +the service configurator get pretty confused. -In detail, the svc.conf file is read and services loaded when +In detail, the svc.conf file is read and services loaded when ORB_init () is called in the main (). But, to load any service, we need to initialize the ORB. Here, it gets confused. To avoid this, run the TAO_Service with no entries in the svc.conf file. @@ -109,7 +109,7 @@ entry, send a SIGHUP signal: svc.conf file again and reconfigures the services. 3. If you want to test if the service is loaded successfully, run the -generic client program < tests_svc_loader.cpp > located in +generic client program < tests_svc_loader.cpp > located in orbsvcs/tests/tests_svc_loader. For more details about the tests_svc_loader.cpp, read the README in the same directory. |