1 This test illustrates how to connect multiple ECs; it has many
2 options and can be configured to run a single EC, two ECs connected
3 through a Gateway, short-circuit the EC, use a global, local or
4 precomputed schedule, etc.
6 Please see the scripts for typical configurations.
8 A simple test is that uses a pre-computed schedule would be:
10 # Run the Naming Service
11 $ ../../Naming_Service/Naming_Service
12 -p NameService.pid -o NameService.ior
13 # If the multicast location does not work for your use:
15 # NameService=`cat NameService.ior`
18 # or other commands that suit your shell.
21 # Run the first EC, supplier generates events <1> and <2> consumer
22 # subscribes to events <1> and <3>
23 $ ./EC_Multiple -l ECM1 -r ECM2 -s runtime -p ECM1.pid \
24 -h 1,1,1,250000,100,1,2,1,3
26 # Run the second EC, supplier generates events <4> and <3> consumer
27 # subscribes to events <4> and <2>
28 $ ./EC_Multiple -l ECM2 -r ECM1 -s runtime -p ECM2.pid \
29 -h 1,1,1,250000,100,4,3,4,2
31 # Notice how the consumer receives both local and remote events, but
32 # not all the local neither all the remote events.