To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106938
                 Issue #|106938
                 Summary|Journalled Recovery
               Component|framework
                 Version|OOO310m19
                Platform|Unknown
                     URL|
              OS/Version|All
                  Status|UNCONFIRMED
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|ENHANCEMENT
                Priority|P3
            Subcomponent|code
             Assigned to|tm
             Reported by|jcobban





------- Additional comments from [email protected] Mon Nov 16 03:04:21 
+0000 2009 -------
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.

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to