diff -r 000000000000 -r 89d6a7a84779 Symbian3/SDK/Source/GUID-1AFDDD6F-CB99-587D-A0B5-D3F5B27F7135.dita --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/Symbian3/SDK/Source/GUID-1AFDDD6F-CB99-587D-A0B5-D3F5B27F7135.dita Thu Jan 21 18:18:20 2010 +0000 @@ -0,0 +1,12 @@ + + + + + +Concepts

This section describes the ideas that underly the Comms Database.

The Comms Database provides system wide storage for communications related settings. The Comms Database holds information about Internet Access Providers (IAPs), Internet Service Providers (ISPs), GPRS, modems, locations, charge-cards, proxies, WAP settings etc. The Comms Database holds this information as a set of related tables.

Symbian OS defines the format of this information, but the Comms Database can also contain user-defined data. Symbian support for user-defined data is limited to backup and security.

Tools and applications that manage voice and data transmissions use the Comms Database.

The Comms Database is a persistent store. Tools and applications use the CommsDat API to access the data in the Comms Database. The CommsDat API hides the structure of the data on the database. The CommsDat API also hides the implementation of the database, and allows the implementation to change in future versions of Symbian OS without a change to client code.

The current version of Symbian OS implements the Comms Database in the Central Repository.

The Comms Database is available on all Symbian platforms.

Configuring comms database using CED Comms database configuration file format
\ No newline at end of file