summaryrefslogtreecommitdiff
path: root/trunk/TAO/orbsvcs/tests/EC_Mcast/README
diff options
context:
space:
mode:
Diffstat (limited to 'trunk/TAO/orbsvcs/tests/EC_Mcast/README')
-rw-r--r--trunk/TAO/orbsvcs/tests/EC_Mcast/README21
1 files changed, 21 insertions, 0 deletions
diff --git a/trunk/TAO/orbsvcs/tests/EC_Mcast/README b/trunk/TAO/orbsvcs/tests/EC_Mcast/README
new file mode 100644
index 00000000000..9f195081d11
--- /dev/null
+++ b/trunk/TAO/orbsvcs/tests/EC_Mcast/README
@@ -0,0 +1,21 @@
+# $Id$
+
+This test can be pretty complicated to run, a sample configuration file is
+included to help you startup.
+
+ The basic idea to remember is that a "Federation" is a logical
+grouping of incoming and outgoing mcast addresses that share the same
+multicast port. The test reads the configuration file to find out
+which Federations are globally available defined, but the comand line
+is used to specify the list of federations that are actually running
+on each process.
+
+ To make the test interesting you should run at least two
+copies of the test, on different windows (to keep the output appart):
+
+$ ./EC_Mcast -p ECM1.pid -c sample.cfg -n 200 -t 500000 -f Set02
+$ ./EC_Mcast -p ECM2.pid -c sample.cfg -n 200 -t 500000 -f Set02
+
+ the test will report the number of events received, if you run
+just one of the processes you will notice that this number is smaller,
+this indicates that some events come from a "remote" event.