LUMIERA.clone/doc/design/lowlevel/index.txt

Design Documents: Vault
=======================

What follows is a summary of Lumiera's *Data Handling Backend*

This is the foundation layer responsible for any high performance or high volume
data access. Within Lumiera, there are two main kinds of data handling:

* The Session and the object models manipulated through the GUI are kept in memory.
  They are backed by a _storage backend,_ which provides database-like storage and
  especially logging, replaying and ``Undo'' of all ongoing modifications..
* Media data is handled _frame wise_ -- prefetching data asynchronously.

The goal is to optimize CPU utilization; large scale data IO will be performed
asynchronously. Data retrieval and processing of prerequisites will
be *scheduled* such as to manage the rendering _just in time_.
Global-Layer-Renaming: adapt lots of documentation 2018-11-15 21:13:52 +01:00			`Design Documents: Vault`
			`=======================`
Move in the existing documentation outline from the Website-repository 2010-11-14 23:19:07 +01:00
Minor grammatical and textual improvements in the documentation. 2013-04-12 03:42:46 +02:00			`What follows is a summary of Lumiera's Data Handling Backend`
remove the superfluous TiddlyWikis ..after integrating all still relevant asciidoced content into the main website. 2012-01-11 06:55:54 +01:00
			`This is the foundation layer responsible for any high performance or high volume`
Minor grammatical and textual improvements in the documentation. 2013-04-12 03:42:46 +02:00			`data access. Within Lumiera, there are two main kinds of data handling:`
remove the superfluous TiddlyWikis ..after integrating all still relevant asciidoced content into the main website. 2012-01-11 06:55:54 +01:00
Minor grammatical and textual improvements in the documentation. 2013-04-12 03:42:46 +02:00			`* The Session and the object models manipulated through the GUI are kept in memory.`
			`They are backed by a _storage backend,_ which provides database-like storage and`
remove the superfluous TiddlyWikis ..after integrating all still relevant asciidoced content into the main website. 2012-01-11 06:55:54 +01:00			especially logging, replaying and ``Undo'' of all ongoing modifications..
DOC: update technical docs to reflect recent development At various places, concepts and drafts from the early stage of the Lumiera Project are still reflected in the online documentation pages. During the last months, development focussed on the Render Engine, causing a shift in some parts of the design, and obsoleting other parts altogether (notably we consider to use IO_URING for async IO) 2023-10-25 00:02:08 +02:00			`* Media data is handled _frame wise_ -- prefetching data asynchronously.`
Move in the existing documentation outline from the Website-repository 2010-11-14 23:19:07 +01:00
DOC: update technical docs to reflect recent development At various places, concepts and drafts from the early stage of the Lumiera Project are still reflected in the online documentation pages. During the last months, development focussed on the Render Engine, causing a shift in some parts of the design, and obsoleting other parts altogether (notably we consider to use IO_URING for async IO) 2023-10-25 00:02:08 +02:00			`The goal is to optimize CPU utilization; large scale data IO will be performed`
			`asynchronously. Data retrieval and processing of prerequisites will`
			`be scheduled such as to manage the rendering _just in time_.`