diff -r ebc84c812384 -r 46218c8b8afa Symbian3/PDK/Source/GUID-F4875493-6501-56FC-90E5-5EEAA89A72C3.dita --- a/Symbian3/PDK/Source/GUID-F4875493-6501-56FC-90E5-5EEAA89A72C3.dita Thu Mar 11 15:24:26 2010 +0000 +++ b/Symbian3/PDK/Source/GUID-F4875493-6501-56FC-90E5-5EEAA89A72C3.dita Thu Mar 11 18:02:22 2010 +0000 @@ -1,13 +1,13 @@ - - - - - -Persistent Storage OverviewProvides application data persistence between sessions.
Purpose

The Persistent Storage collection contains various solutions to the problem of persisting application data.

Architecture

The components of the Persistent Storage collection are mainly independent of each other from an architectural point of view. The only exception to this is that the relational database functionality provided by DBMS makes use of stores. However, that is a matter of implementation: the two components are alternative solutions to data persistence and are not used in combination.

Description

The functionality of each component is threefold:

  • Writing application data to memory,

  • Reading application data from memory, and

  • Managing data integrity when several applications are reading from or writing to memory using the same component.

Components
  • Central Repository persists application data using repositories created at build time.

  • Store persists application data using data streams.

  • DBMS persists application data using relational databases.

  • SQL persists application data using relational databases.

  • SQLite persists application data using relational databases.

Using Persistent Storage

The components of this collection are all used for the same purpose, persisting application data. They differ in the strategy used and in their implementation.

Central Repository + + + + + +Persistent Storage OverviewProvides application data persistence between sessions.
Purpose

The Persistent Storage collection contains various solutions to the problem of persisting application data.

Architecture

The components of the Persistent Storage collection are mainly independent of each other from an architectural point of view. The only exception to this is that the relational database functionality provided by DBMS makes use of stores. However, that is a matter of implementation: the two components are alternative solutions to data persistence and are not used in combination.

Description

The functionality of each component is threefold:

  • Writing application data to memory,

  • Reading application data from memory, and

  • Managing data integrity when several applications are reading from or writing to memory using the same component.

Components
  • Central Repository persists application data using repositories created at build time.

  • Store persists application data using data streams.

  • DBMS persists application data using relational databases.

  • SQL persists application data using relational databases.

  • SQLite persists application data using relational databases.

Using Persistent Storage

The components of this collection are all used for the same purpose, persisting application data. They differ in the strategy used and in their implementation.

Central Repository Overview DBMS Overview Store Overview Symbian SQL Overview SQLite 3 Overview
\ No newline at end of file