Changes between Version 3 and Version 4 of Old/Documentation/OTG/FuncSpec/OmlIntegration

Timestamp:

Oct 6, 2005, 5:59:15 PM (19 years ago)

Author:

zhibinwu

Comment:

—

Old/Documentation/OTG/FuncSpec/OmlIntegration

@@ -7 +7 @@
 To isolate/encapsulate all OML-related functions, a class [source:otg/trunk/src/cpp/orbitapp.h#latest OrbitApp] is designed.
 All other design components/objects shall not care about measurements reporting mechanism and the interaction with OML. 
-This class derived three child classes for respective appliactions.
+This class derived three child classes for respective applications.
 
 [[Image(classOrbitApp.png)]] [[BR]]
@@ -14 +14 @@
 == Implementation ==
 
-All functons to call OML are put as pure virtual functions in this base class. OTG/OTR/OTFApp can select to implement a subset of those functions. This design has some advantages:
+All functions to call OML are put as pure virtual functions in this base class. OTG/OTR/OTFApp can select to implement a subset of those functions. This design has some advantages:
  * to make OTF to reuse the Stream/Port/Gate structure of as a combination of OTG/OTR
  * to share some common functions for all OTG/OTR/OTFApp, such as close()
 
-The class has a boolean varialbe to indicate if OML will be used or not. If it is false, all measurement reports will be redireted to a local log file. This is a special debugging mode. And it could also be served as a means to use OTG outside of ORBIT testbed.
+The class has a Boolean variable to indicate if OML will be used or not. If it is false, all measurement reports will be redirected to a local log file. This is a special debugging mode. And it could also be served as a means to use OTG outside of ORBIT testbed.
 
 OML calls are actually implemented externally by OML-client libraries. So, special header files are fetched dynamically in compilation. Those header files have to be included here. For example: