|
|||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
AppFaultManager | This interface is used to inform the application of events that affect the integrity of the Framework, Service or Client Application. |
AppHeartBeat | The Heartbeat Application interface is used by the Framework to send the client application its heartbeat. |
AppHeartBeatMgmt | This interface allows the initialisation of a heartbeat supervision of the client application by the framework. |
AppLoadManager | The client application developer supplies the load manager application interface to handle requests, reports and other responses from the framework load manager function. |
AppOAM | The OAM client application interface is used by the Framework to query the application date and time, for synchronisation purposes. |
FaultManager | This interface is used by the application to inform the framework of events that affect the integrity of the framework and services, and to request information about the integrity of the system. |
HeartBeat | The Heartbeat Framework interface is used by the client application to send its heartbeat. |
HeartBeatMgmt | This interface allows the initialisation of a heartbeat supervision of the framework by a client application. |
LoadManager | The framework API should allow the load to be distributed across multiple machines and across multiple component processes, according to a load management policy. |
OAM | The OAM interface is used to query the system date and time. |
Contains the Parlay Framework-to-Application Iintegrity Management interfaces.
|
|||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |