Storage; Random Access Memory; Volatile File Storage (Cache Disk) - Motorola MC9500-K Integrator Manual

SampleCpy.xml
<wap-provisioningdoc>
<characteristic type= "FileOperation">
<characteristic type= "\Windows" translation= "filesystem">
<characteristic type= "MakeDir"/>
<characteristic type= "example.txt" translation= "fileystem">
</characteristic>
</characteristic>
</characteristic>
</wap-provisioningdoc>

Storage

Mobile 6 contains three types of file storage:
•
Random Access Memory (RAM)
•
Persistent Storage
•
Application folder.

Random Access Memory

Executing programs use RAM to store data. Data stored in RAM is lost upon a warm boot. RAM also included a
volatile file storage area called Cache Disk.

Volatile File Storage (Cache Disk)

Windows Mobile 6 memory architecture uses persistent storage for all files, registry settings, and database objects
to ensure data is retained even after a power failure. Persistent storage is implemented using Flash memory
technology which is generally slower than volatile RAM memory. In certain situations the speed of the operation is
more important than the integrity of the data. For these situations, Motorola has provided a small volatile File
Storage volume, accessed as the Cache Disk folder. Disk operations to the Cache Disk folder are much faster than
to any of the persistent storage volumes, but data is lost across warm boots and power interruptions. Note that a
backup battery powers RAM memory, including the Cache Disk, when you remove the main battery for a short
period of time.
The MC9500-K uses the Cache Disk for temporary data that can be restored from other sources, for example, for
temporarily "caching" HTML web pages by a browser or generating formatted files to send to a printer. Both
situations benefit from the increased speed of the cache disk, but you can restore the data if needed.
DO NOT use the Cache Disk as a method to improve application performance. Analyze applications that perform
slower in persistent storage to optimize disk access. Common areas for optimization include minimizing the
number of reads and writes to a file, removing unneeded debug logging, and minimizing file flushing or closing
files.
<characteristic type= "Copy">
<parm name= "Source" value= "\Application\example.txt" translation= "filesystem"/>
</characteristic>
Application Deployment for Mobile 6 4 - 9