DMT Services Service Libraries
| AppClient Application client API. | |
| AppServer Application server class | |
| Monitor Data Monitor Client and Server APIs | |
| Name Client Name Client API | |
| Name Server DMT Name to Address Translation Service | |
| Tunnel LMSG network message bridge. | |
| Frame IO Read and write frames | |
| Trend Frames Read and write trend frames | |
| Web Server Serve formatted Monitor data objects to a web browser | |
| Trigger Client Trigger Manager client API | |
| Alarm Client Alarm Manager client API | |
| Trigger Manager Trigger record broker. | |
| fantom Frame and NDS translation module | |
| DFM low level API (fantom) DFM low level API (fantom) |
The DMT Services libraries provide interfaces to allow DMT monitors to communicate with the outside world. The DMT Service libraries contain:
- Application client and server APIs.
- DMT Monitor data client and server APIs.
- DMT Name Server and client API.
- DMT Trigger Manager and client API.
- DMT Alarm Manager and Client API.
- Data access API
- Frame writer API
- Trend frame reader and writer APIs.
The service class source code is available from CVS The following libraries are produced:
libclient.so libclient.a Alarm, Monitor Data and Name client APIs and the AppClient API. libframeio.so libframeio.a Data Accessor, Frame writer, Trend I/O and associated classes. libmonitor.so basic subset of monitor classes including Monitor data server, name client, Alarm Client and necessary support classes. libtclient.so libtclient.a Trigger client class (needs external ProcID)
alphabetic index hierarchy of classes
Please send questions and comments to zweizig_j@ligo.caltech.edu
generated by doc++