blob: 605ac2c126021cd80e0c60f9cde9dd77cb2d27ed (
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
|
This test verifies that the "PICurrent" object semantics are correct
on both the client side and the server side. In particular, it
attempts to make sure the request scope current (RSC) and thread scope
current (TSC) copying semantics are correct when transitioning between
the two scopes on both the client and server sides. This is
accomplished by setting and getting elements of different types in the
RSC and TSC slot tables at various points during the course of an
invocation.
Expected output is along the lines of the following:
==== Running PICurrent test
PICurrentTest::test: <IOR:010000001b000000...>
(9378|1078768288) Extracted <46> from RSC slot 0
(9378|1078768288) Client side RSC/TSC semantics appear to be correct.
(9377|1080582944) Inserted number <62> into RSC.
Test method invoked.
(9377|1080582944) Retrieved number <62> from TSC.
(9377|1080582944) Extracted <62> from RSC slot 0
(9377|1080582944) RSC->TSC->RSC copying appears to be working.
(9377|1080582944) String "Drink milk!" inserted into TSC.
(9377|1080582944) Retrieved "Drink milk!" from the RSC.
(9377|1080582944) Server side RSC/TSC semantics appear to be correct.
(9378|1078768288) Retrieved "Et tu Brute?" from the TSC.
(9377|1080582944) Server is shutting down.
Event loop finished.
|
