summaryrefslogtreecommitdiff
path: root/TAO/tests/OBV/Supports/README
diff options
context:
space:
mode:
authoredwardgt <edwardgt@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2003-09-14 22:09:10 +0000
committeredwardgt <edwardgt@ae88bc3d-4319-0410-8dbf-d08b4c9d3795>2003-09-14 22:09:10 +0000
commit1e50200fbc3649408ca55a7a168ba8dd387e73ec (patch)
treec8ab81468a35c4f00c1b9fae8c4fd00c7ef2e70d /TAO/tests/OBV/Supports/README
parent8d2d864708e4af0a0d5ce4c05032629974910e33 (diff)
downloadATCD-1e50200fbc3649408ca55a7a168ba8dd387e73ec.tar.gz
ChangeLogTag: Sun Sep 14 17:01:31 2003 George Edwards <g.edwards@vanderbilt.edu>
Diffstat (limited to 'TAO/tests/OBV/Supports/README')
-rw-r--r--TAO/tests/OBV/Supports/README5
1 files changed, 1 insertions, 4 deletions
diff --git a/TAO/tests/OBV/Supports/README b/TAO/tests/OBV/Supports/README
index 6256d7c6be8..e708dff9ed8 100644
--- a/TAO/tests/OBV/Supports/README
+++ b/TAO/tests/OBV/Supports/README
@@ -10,7 +10,7 @@ probably not define an implementation of the interface. Doing so will result in
multiple implementations of the same method - one for objects of the interface,
and one for valuetypes - and clients will have no way to distiguish between the
two, other than narrowing objects of the interface type to the
-valuetype. Instead, leave the interface unimplemented, and only define
+valuetype. Instead, one can leave the interface unimplemented, and only define
implementations of its methods in the valuetype.
The steps are as follows:
@@ -30,6 +30,3 @@ Supports_Test checks proper operation of the following features:
-ORB::register_value_factory () return values:
Supports_Test checks the return values of register_value_factory () to
ensure compliance with the spec.
--Multithreading:
- If the run_test.pl script is used, several clients will be spawned and the
- server will used a thread-per-connection model. \ No newline at end of file