Symbian3/PDK/Source/GUID-D8CC5B36-41DA-5989-8FA8-3F56306146A3.dita
changeset 5 f345bda72bc4
parent 3 46218c8b8afa
child 14 578be2adaf3e
equal deleted inserted replaced
4:4816d766a08a 5:f345bda72bc4
     7     Nokia Corporation - initial contribution.
     7     Nokia Corporation - initial contribution.
     8 Contributors: 
     8 Contributors: 
     9 -->
     9 -->
    10 <!DOCTYPE concept
    10 <!DOCTYPE concept
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">
    12 <concept xml:lang="en" id="GUID-D8CC5B36-41DA-5989-8FA8-3F56306146A3"><title>Introduction to stores</title><prolog><metadata><keywords/></metadata></prolog><conbody><p>A store is a collection of streams and is a fundamental part of the operating system. </p> <p>Stores are used to implement the persistence of objects. Typically, a store is a file, although an in-memory store is provided. A store can also be embedded as a stream within another store; this is a more advanced aspect of stores.</p> <p>For many purposes, stores replace the direct use of files and the file server client side API, although other features of the file server are still relevant. Stores are a key building block for the application architecture because they provide the support necessary for embedded documents.</p> <p>The basic behaviour of stores is encapsulated by the <codeph>CStreamStore</codeph> class and provides the core abstract framework that allows streams to be manipulated. Each class derived from <codeph>CStreamStore</codeph> implements the parts of the API that are appropriate.</p> <p>A number of stores are defined that build on <codeph>CStreamStore</codeph>. Some of the most important are: <codeph>CPersistentStore</codeph>, <codeph>CFileStore</codeph>, <codeph>CDirectFileStore</codeph>, <codeph>CPermanentFileStore</codeph>, <codeph>CEmbeddedStore</codeph>, <codeph>CBufStore</codeph>. Each has various capabilities.</p> <p>A store is also the basis of the relational database provided by DBMS.</p> </conbody></concept>
    12 <concept id="GUID-D8CC5B36-41DA-5989-8FA8-3F56306146A3" xml:lang="en"><title>Introduction
       
    13 to Stores</title><shortdesc>A store is a collection of streams and is a fundamental part of
       
    14 the operating system.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody>
       
    15 <p>Stores are used to implement the persistence of objects. Typically, a store
       
    16 is a file, although an in-memory store is provided. A store can also be embedded
       
    17 as a stream within another store; this is a more advanced aspect of stores.</p>
       
    18 <p>For many purposes, stores replace the direct use of files and the File
       
    19 Server Client Side API, although other features of the file server are still
       
    20 relevant. Stores are a key building block for the application architecture
       
    21 because they provide the support necessary for embedded documents.</p>
       
    22 <p>The basic behaviour of stores is encapsulated by the <codeph>CStreamStore</codeph> class
       
    23 and provides the core abstract framework that allows streams to be manipulated.
       
    24 Each class derived from <codeph>CStreamStore</codeph> implements the parts
       
    25 of the API that are appropriate.</p>
       
    26 <p>A number of stores are defined that build on <codeph>CStreamStore</codeph>.
       
    27 Some of the most important are: <codeph>CPersistentStore</codeph>, <codeph>CFileStore</codeph>, <codeph>CDirectFileStore</codeph>, <codeph>CPermanentFileStore</codeph>, <codeph>CEmbeddedStore</codeph>, <codeph>CBufStore</codeph>. Each has various
       
    28 capabilities.</p>
       
    29 <p>A store is also the basis of the relational database provided by DBMS.</p>
       
    30 </conbody></concept>