Symbian3/SDK/Source/GUID-83E4F989-0B73-5E83-8547-AB3070492CBF.dita
changeset 2 ebc84c812384
parent 0 89d6a7a84779
equal deleted inserted replaced
1:25a17d01db0c 2:ebc84c812384
    10 <!DOCTYPE task
    10 <!DOCTYPE task
    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Task//EN" "task.dtd">
    12 <task id="GUID-83E4F989-0B73-5E83-8547-AB3070492CBF" xml:lang="en"><title>What
    12 <task id="GUID-83E4F989-0B73-5E83-8547-AB3070492CBF" xml:lang="en"><title>What
    13 is the Comms Database?</title><shortdesc>The Comms Database contains the information necessary to configure
    13 is the Comms Database?</title><shortdesc>The Comms Database contains the information necessary to configure
    14 components in the comms stack. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
    14 components in the comms stack. </shortdesc><prolog><metadata><keywords/></metadata></prolog><taskbody>
    15 <context><p>The Comms Database has a set of parameters used
    15 <context id="GUID-CA4E76D5-2505-48F7-A205-BA42A93FD92B"><p>The Comms Database has a set of parameters used to configure communications
    16 to configure communications on Symbian OS. The information stored in the Comms
    16 on Symbian platform. The information stored in the Comms Database
    17 Database is used to configure components in the comms stack. Information such
    17 is used to configure components in the comms stack. Information such as connection
    18 as connection preferences, account settings and some of the linkage between
    18 preferences, account settings and some of the linkage between components can
    19 components can be set in the comms stack. The configuration data is stored
    19 be set in the comms stack. The configuration data is stored in records in
    20 in records in database tables. The data also has data schema to define the
    20 database tables. The data also has data schema to define the tables. For more
    21 tables. For more information and a full list of the settings in the Comms Database,
    21 information and a full list of the settings in the Comms Database, see the <xref href="GUID-58089281-9DD0-502D-8DFD-831E7BAA931E.dita">Reference</xref></p><p>The
    22 see the <xref href="GUID-58089281-9DD0-502D-8DFD-831E7BAA931E.dita">Reference</xref></p><p>The
       
    23 Comms Database is configured in one of the following ways: </p> <ul>
    22 Comms Database is configured in one of the following ways: </p> <ul>
    24 <li id="GUID-3CFE8D23-F087-54D1-A6F3-83EDD0510609"><p>It is compiled from
    23 <li id="GUID-3CFE8D23-F087-54D1-A6F3-83EDD0510609"><p>It is compiled from
    25 a definition file into a binary file to ship in the ROM of a device. For more
    24 a definition file into a binary file to ship in the ROM of a device. For more
    26 information about how to compile the default version of the database see <xref href="GUID-00696F18-F1C8-5810-A9F9-E7215CA451A4.dita">Configuring comms database
    25 information about how to compile the default version of the database see <xref href="GUID-00696F18-F1C8-5810-A9F9-E7215CA451A4.dita">Configuring comms database
    27 using CED and CEDDUMP</xref>. </p> </li>
    26 using CED and CEDDUMP</xref>. </p> </li>