summaryrefslogtreecommitdiff
path: root/TAO/tests/NestedUpcall/Triangle_Test/README
blob: 70e8d57e5fe4f8b37580374a5688e16fa4f45b0c (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
$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