1 files changed, 46 insertions, 0 deletions
diff --git a/TAO/performance-tests/Cubit/TAO/DII_Cubit/README b/TAO/performance-tests/Cubit/TAO/DII_Cubit/README
new file mode 100644
index 00000000000..1ca7a98a2fe
--- /dev/null
+++ b/TAO/performance-tests/Cubit/TAO/DII_Cubit/README
@@ -0,0 +1,46 @@
+// $Id$
+
+This is the cubit example that does everything using DII requests. 
+It uses the server in IDL_Cubit. The initial call to resolve the 
+nameservice is made on the orb. After that, getting a reference
+to the Cubit object, making the Cubit operation calls, 
+and shutting down the server are all done with DII requests.
+
+To run the tests with one "button-push", execute the perl script run_test.pl
+in this directory. It will start up the server and client. The client will
+shut down the server when the tests are finished.
+
+If you want to run each executable separately and manually, run the 
+server first (in IDL_Cubit). Then run the client with zero or more of 
+the following args:
+
+        [-d]                 Increments TAO_debug_level. It's additive, up
+                             to 2 levels of debugging.
+
+        [-n <calls/loop>]	   Sets the # of calls per loop (default is 250).
+
+        [-i <factory IOR>]   For passing the IOR by hand.
+
+        [-f <filename>]      If server is run with [-o <filename>] option, 
+                             it outputs its factory IOR to a file, which
+                             the client can readwith this option.
+
+        [-x]                 Shuts down server when finished.
+
+        [-s]                 Disables use of the TAO naming service (-i and
+                            -f options do this automatically).
+
+If using the -i option, you might want to run the server with the option 
+[-ORBobjrefstyle url]. This will cause the server to display its IOR in a 
+more human-readable form. Make sure you use the factory IOR, NOT the nameservice 
+IOR. The server displays both. The server can be run in the same window in the 
+background, or in a different window.
+
+The command line options, default calls per loop, order and display format of the 
+stats are all similar to those in the IDL_Cubit tests.
+
+On the Unix side, the Makefile will also build IDL_Cubit/server if
+necessary (thanks to David Levine). If the server exits when run on a
+Unix machine, it probbly means that someone else is also running it 
+and the defaults port numbers have collided. Just add the arg
+[-ORBport 0] when running the server and it will get a new port number.