Storage Concept

Conceptual Concerns

With #37 , there are general concerns on the storage concept which should be clarified before releasing this page to user documentation.

Situation

An application maintains data that shall be persisted during sessions. But there are more details to consider. Shall the data be stored human readable or in binary format? Shall it be encrypted? Shall it be shared with other application instances?

Approach

The storage concept is an abstraction allowing you to focus on the function your are implementing and pick the storage behavior from the APPXC library. The behavior is split into storage locations:

• on local disk (LocalStorage) or

• via FTP, storage format (also called the serialization method):

• as binary (via TBD) or

• human readable as JSON file and additional methods:

• locally encrypted (see [[Login for Local Encryption]])

• shared storage that includes meta data [[Data Synchronization]]

  • without encryption

  • with encryption based on [[User Registry]]

• encrypted for remote shares (see [[User Registry]])

Guide

Your Functionality

Recommended is to encapsulate your functions into a class. If you want to use other ways, see the APPXC storage concept details below.

Storage Concept

Ideally, your function is enclosed in a class that derives from APPXC Storable and forwards necessary initialization information and satisfies the interfaces. Then, when instantiating your class, you define the actual Storage behavior.

v0.0.4.dev4