Alarm Server Overview

Provides alarm services.

The API is used by the Agenda Model API.

The API has two key concepts: alarm server, and alarm.

The alarm server manages the alarms on the system. Clients can connect to the server to get information about the alarms, set and cancel alarms, and set the alarm sound state.

The client interface to the alarm server is provided by RAlarmServer.

An alarm has a number of properties:

• type

• agenda: general alarms for application use; they persist beyond the session that created them

• clock: 8 alarms used by the ER5 Time application

• session: exist for the duration of the client's session with the server

• orphaned: a session alarm relinquished by the client to the server, so that it can be serviced after the session closes

• due time

• time: this can differ from the due time, after the alarm has been snoozed

• message to display to user

• sound file to play when the alarm activates

• repeat behaviour (for clock alarms)

The alarm interface is provided by TAlarmInfo, or by directly passing alarm properties to alarm server functions.

Agenda File Overview

Client/Server Overview