Issue 106938 - Journalled Recovery
Summary: Journalled Recovery
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOO310m19
Hardware: Unknown All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Keywords: needhelp
Depends on:
Reported: 2009-11-16 03:04 UTC by jcobban
Modified: 2014-01-28 11:47 UTC (History)
2 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description jcobban 2009-11-16 03:04:21 UTC
OOo uses a periodic save recovery mechanism.  This has two deficiencies:

1) For significant sized documents the periodic save interrupts the user's work.
2) If it is ever invoked any work performed by the user since the last save is
lost and must be reentered by the user.

Both of these concerns impact on the productivity of users.

Although periodic save is characteristic of competing products, I believe that
OOo should exceed the marketplace.

As a counter-example all current popular file systems, with the exception of
FAT, use journaling to minimize lost data during a system failure.

I am surprised that this requirement does not appear to have been considered,
even if there are valid reasons that I am unaware of to defer implementation.
Comment 1 thorsten.martens 2009-11-16 09:53:26 UTC
TM->CD: please have a look, thanks !