Top-level classes, structs, unions and interfaces with brief
descriptions:
Offers various methods to obtain alarm information from both
control system servers and central alarm servers |
|
TINE Data Type object: All data transfered client between and
server must be contained in a TDataType
object |
|
TEquipmentModule
is the a TINE server's equipment module class |
|
Offers various methods to obtain archived data from both control
system servers and central archivers |
|
TKernel
is the TINE Kernel (singleton) class, whose static methods are used to manage
the TINE engine |
|
Defines a connection between the local client and the remote
server's targeted end point |
|
TQuery
is a singleton class offering static methods to acquire information from the
control system elements |
|
Represents a TINE tagged structure |
|
A Class which acquires and manages scope trace information |
Most calls and methods familiar to the C/C++ programmer are to be
found in one form or another within the TKernel
class. In general, client-side
applications will want to stick with instantiating a TLink object and making use of
its methods and callback handlers.
Server applications will need to instantiate one or more TEquipmentModule
objects and handlers and make use of their methods. A FEC (front end controller) can be
registered as always via configuration (fecid.csv or fec.xml) of via API calls
found in TKernel.
Data objects can be used to instantiate the TDataType
objects needed for client or server calls.
User-defined tagged structures can be easily instantiated (following the
paradigms in the examples shown in within the TTaggedStruct class) and likewise used to instantiate a TDataType
object.