Slide 4.2: Persistent storage   Slide 4.4: Programming with the RMS   Home

Record Management Systems

---

Working with Threads
The MIDP RMS implementation ensures that all individual record store operations are atomic, synchronous, and serialized, so no corruption occurs with multiple access. However, if your MIDlets use multiple threads to access a record store, it is your responsibility to synchronize this access.

The RMS Package
The RMS package consists of the following four interfaces, one class, and five exception classes:

Interfaces

• RecordComparator: Defines a comparator to compare two records.
• RecordEnumeration: Represents a bidirectional record enumerator.
• RecordFilter: Defines a filter to examine a record and checks if it matches based on a criteria defined by the application.
• RecordListener: Receives records which were added, changed, or deleted from a record store.

Classes

RecordStore: Represents a record store.

Exceptions

• InvalidRecordIDException: Thrown to indicate the RecordID is invalid.
• RecordStoreException: Thrown to indicate a general exception was thrown.
• RecordStoreFullException: Thrown to indicate the record store file system is full.
• RecordStoreNotFoundException: Thrown to indicate the record store could not be found.
• RecordStoreNotOpenException: Thrown to indicate an operation on a closed record store.