Issue 102604

Summary: Optimising OOo's saving mechanism for quick saves.
Product: General Reporter: de_logics <de_logics>
Component: codeAssignee: AOO issues mailing list <issues>
Status: UNCONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: elish, issues
Version: OOo 3.1Keywords: needhelp
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---

Description de_logics 2009-06-09 06:35:42 UTC
It can be seen that in large documents OOo takes a very long time to save the
document no matter how small the changes are.

The reason for this is cause OOo does not use increment saving, i.e it recreates
the whole file (like in a save as operation) and then recompresses it........all
this while the user has to wait.

If the document is made to edit while the save operation is on, this problem can
be easily eliminated.
Comment 1 tml 2009-06-10 10:10:03 UTC
Comment 2 de_logics 2009-06-12 08:59:31 UTC
I mean as compared to implementing increment saving, that will mean you have
rethink the work on the whole saving mechanism.