647
edits
Changes
Jump to navigation
Jump to search
Development Team/Datastore Rewrite (view source)
Revision as of 07:54, 23 September 2008
, 07:54, 23 September 2008New page: == Goals == === Reliability === A good DataStore doesn't lose data easily. === Performance === Queries should be fast enough for the journal to be very responsive when browsing its con...
== Goals ==
=== Reliability ===
A good DataStore doesn't lose data easily.
=== Performance ===
Queries should be fast enough for the journal to be very responsive when browsing its contents.
Activities should be able to store their data quickly and present a fast UI to their users.
The shell should be able to quickly query the DS to allow the user to resume entries from other views than the journal.
=== Custom metadata properties ===
Activities should be able to store in their entries the metadata they wish, should not be limited to a predefined set.
=== More efficient file storage ===
Identical files should be stored just once.
=== Versioned entries (not fulfilled yet) ===
Entries may be related in version trees.
== Design ==
=== Reliability ===
A good DataStore doesn't lose data easily.
=== Performance ===
Queries should be fast enough for the journal to be very responsive when browsing its contents.
Activities should be able to store their data quickly and present a fast UI to their users.
The shell should be able to quickly query the DS to allow the user to resume entries from other views than the journal.
=== Custom metadata properties ===
Activities should be able to store in their entries the metadata they wish, should not be limited to a predefined set.
=== More efficient file storage ===
Identical files should be stored just once.
=== Versioned entries (not fulfilled yet) ===
Entries may be related in version trees.
== Design ==