Issue 102604 - Optimising OOo's saving mechanism for quick saves.
Summary: Optimising OOo's saving mechanism for quick saves.
Status: UNCONFIRMED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: OOo 3.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: needhelp
Depends on:
Blocks:
 
Reported: 2009-06-09 06:35 UTC by de_logics
Modified: 2014-02-06 19:58 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
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 
"easily"?
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.