summaryrefslogtreecommitdiff
path: root/TAO/tests/NestedUpcall/Triangle_Test/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/tests/NestedUpcall/Triangle_Test/README')
-rw-r--r--TAO/tests/NestedUpcall/Triangle_Test/README31
1 files changed, 0 insertions, 31 deletions
diff --git a/TAO/tests/NestedUpcall/Triangle_Test/README b/TAO/tests/NestedUpcall/Triangle_Test/README
deleted file mode 100644
index 70e8d57e5fe..00000000000
--- a/TAO/tests/NestedUpcall/Triangle_Test/README
+++ /dev/null
@@ -1,31 +0,0 @@
-$Id$
-Documentation about the Triangle test
-
-Purpose:
-
-Is to show how nested upcalls are handled.
-
-Three objects exist:
-Object A, Object B and the Initiator
-
-The initiator calls a two-way call foo on object A,
-object A calls foo_object_B, a one-way call, on the initiator,
-this causes initiator to call foo on object B,
-this causes object B to (oneway) call finish on object A,
-this causes object A to return from its first two-way call
-(before object B returns from its two-way call),
-after a second or so object B returns from its two-way call.
-
-The printed order should show, that the replies are
-handled in the stack order, but not in the actual
-arriving order.
-
-To start:
-
-%server_A -o server1 -ORBport 10045
-%
-%server_B -o server2 -ORBport 10046
-%
-%initiator -f server1 -g server2 -ORBport 10047
-
- \ No newline at end of file