From bd41a9f1db4e027645b3d558dda2f8e8d2545c28 Mon Sep 17 00:00:00 2001 From: naga Date: Tue, 17 Feb 1998 00:15:55 +0000 Subject: *** empty log message *** --- TAO/tests/Cubit/TAO/IDL_Cubit/README | 13 ++----------- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/TAO/tests/Cubit/TAO/IDL_Cubit/README b/TAO/tests/Cubit/TAO/IDL_Cubit/README index bdbff9ee0a2..39c5da31bba 100644 --- a/TAO/tests/Cubit/TAO/IDL_Cubit/README +++ b/TAO/tests/Cubit/TAO/IDL_Cubit/README @@ -8,19 +8,12 @@ factory object reference. You can either run the server in the background in the same window as the client or open a separate window for the client and server. -Now the server and client can also make use of the Naming service. -You need to start the - TAO/orbsvcs/Naming_service/Naming_service -before running the server and the client to make use of the Namingservice. server: ------- % server [-d] [-ORBhost ] [-ORBport ] - [-n ] [-o ] [-s] - --s option tells the server to bind the cubit_factory name under the -NamingService. + [-n ] [-o ] The server cubit factory maintains num_of_cubit objects (default = 1). They are assigned keys that look like "key0", "key1", ... @@ -44,10 +37,8 @@ Irrespective of the -o option the IOR will be outputted on the screen. client: ------- -% client [-d] [-s] <-f cubit_factory_ior_file> <-k cubit_factory_ior> -n +% client [-d] <-f cubit_factory_ior_file> <-k cubit_factory_ior> -n - -s flag tells the client to get the cubit_factory key from the NamingService. - There are 2 ways of giving the CubitFactory IOR to the client: 1. From a file using the -f option. (This file can be produced using -- cgit v1.2.1