12 <concept id="GUID-1AFDDD6F-CB99-587D-A0B5-D3F5B27F7135" xml:lang="en"><title>Concepts</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>This section describes the ideas that underly the Comms Database. </p> <p>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. </p> <p>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. </p> <p>Tools and applications that manage voice and data transmissions use the Comms Database. </p> <p>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. </p> <p>The current version of Symbian OS implements the Comms Database in the Central Repository. </p> <p>The Comms Database is available on all Symbian platforms. </p> <fig id="GUID-51EC89D3-B9BF-5074-95C7-8C8304626F6E"><image href="GUID-DF83E798-408C-5E69-9520-A733DAEAB788_d0e90726_href.png" placement="inline"/></fig> </conbody><related-links><link href="GUID-00696F18-F1C8-5810-A9F9-E7215CA451A4.dita"><linktext>Configuring comms database using CED</linktext> </link> <link href="GUID-A0948145-32C3-5754-B76D-AD7A8AF001A2.dita"><linktext>Comms database configuration file format</linktext> </link> </related-links></concept>

    12 <concept id="GUID-1AFDDD6F-CB99-587D-A0B5-D3F5B27F7135" xml:lang="en"><title>Concepts</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    13 <p>This section describes the ideas that underly the Comms Database. </p>

    14 <p>The Comms Database provides system wide storage for communications related

    15 settings. The Comms Database holds information about Internet Access Providers

    16 (IAPs), Internet Service Providers (ISPs), GPRS, modems, locations, charge-cards,

    17 proxies, WAP settings etc. The Comms Database holds this information as a

    18 set of related tables. </p>

    19 <p>Symbian platform defines the format of this information, but the Comms

    20 Database can also contain user-defined data. Symbian support for user-defined

    21 data is limited to backup and security. </p>

    22 <p>Tools and applications that manage voice and data transmissions use the

    23 Comms Database. </p>

    24 <p>The Comms Database is a persistent store. Tools and applications use the

    25 CommsDat API to access the data in the Comms Database. The CommsDat API hides

    26 the structure of the data on the database. The CommsDat API also hides the

    27 implementation of the database, and allows the implementation to change in

    28 future versions of Symbian platform without a change to client code. </p>

    29 <p>The current version of Symbian platform implements the Comms

    30 Database in the Central Repository. </p>

    31 <p>The Comms Database is available on all Symbian platforms. </p>

    32 <fig id="GUID-51EC89D3-B9BF-5074-95C7-8C8304626F6E">

    33 <image href="GUID-DF83E798-408C-5E69-9520-A733DAEAB788_d0e114259_href.png" placement="inline"/>

    34 </fig>

    35 </conbody><related-links>

    36 <link href="GUID-00696F18-F1C8-5810-A9F9-E7215CA451A4.dita"><linktext>Configuring

    37 comms database using CED</linktext></link>

    38 <link href="GUID-A0948145-32C3-5754-B76D-AD7A8AF001A2.dita"><linktext>Comms database

    39 configuration file format</linktext></link>

    40 </related-links></concept>