diff -r 80ef3a206772 -r 48780e181b38 Symbian3/SDK/Source/GUID-39A8FBC9-5FD6-4F92-B71E-5C5438ECFD46.dita --- a/Symbian3/SDK/Source/GUID-39A8FBC9-5FD6-4F92-B71E-5C5438ECFD46.dita Fri Jul 16 17:23:46 2010 +0100 +++ b/Symbian3/SDK/Source/GUID-39A8FBC9-5FD6-4F92-B71E-5C5438ECFD46.dita Tue Jul 20 12:00:49 2010 +0100 @@ -12,14 +12,14 @@ OOM Monitor OverviewThis section provides an overview of the functionality and the architecture of the OOM Monitor component. -
Purpose

The +

Purpose

The OOM Monitor Client API monitors the memory situations and handles out of memory situations. OOM monitor is responsible to maintain good memory level in the device. In case of low memory situation, OOM Monitor releases memory by closing applications based on the priority defined. For information on priority, refer to OOM Monitor Priority.

-
Key concepts
+
Key concepts
LOW_RAM_THRESHOLD

It is the minimum amount of free RAM that is specified for the device. @@ -39,19 +39,19 @@

For information on OOM Monitor Priority and Optional RAM allocation, refer to OOM Monitor Concepts

-
Architecture

The +

Architecture

The basic function of the OOM Monitor is to monitor the amount of free RAM in the mobile device. Whenever the amount of free RAM decreases below a defined LOW_RAM_THRESHOLD threshold value, the OOM Monitor is triggered. The OOM Monitor then releases RAM by closing applications running on background in order to raise the amount of free RAM above the defined GOOD_RAM_THRESHOLD value.

- + - +
-
APIs

The +

APIs

The OOM Monitor Client API consists of ROomMonitorSession class. -The main functions of this class are:

+The main functions of this class are:

@@ -74,7 +74,7 @@

The OOM Monitor Client API also consists of COomMonitorPlugin class. -The main functions of this plug-in class are:

+The main functions of this plug-in class are: