From b5a1bb386c47733bc39d4b3e0b5c46e678f5fb42 Mon Sep 17 00:00:00 2001 From: Ichthyostega Date: Thu, 3 Jan 2013 09:25:20 +0100 Subject: [PATCH] DOC/Intro: add some details regarding session storage --- doc/user/intro/intro.txt | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/user/intro/intro.txt b/doc/user/intro/intro.txt index 1ece14a34..a164ee8e9 100755 --- a/doc/user/intro/intro.txt +++ b/doc/user/intro/intro.txt @@ -367,15 +367,15 @@ steps might even be a possibility. For example, work on a project at the office and work on the same project at home can be merged each morning and evening. -Session storage is envisaged to be performed as database with logging, some -search facilities and a number of features associated with databases. +Session storage is envisaged to operate similar to a database or journalling +file system. Any operation will be logged prior to execution. This protects +the session contents against corruption and allows for automated recovery +in case of a crash. The actual storage is delegated to several back-ends. +One of these back-ends implements a _binary storage format_ for performance +reasons, while another one exposes all of the session contents in textual, +human readable form. The storage format is designed in a way to ensure +a certain degree of compatibility while the application evolves. -[red]#Details to be written# -//database with logging, no data loss. -// not generateable data - -// its the timeline mostly -// session storage [[placement]]