https://bz.apache.org/ooo/show_bug.cgi?id=126757
orcmid <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from orcmid <[email protected]> --- (In reply to david.vogt from comment #0) > So, instead of checking the modification time, wouldn't it be a better idea > to look at a checksum of the file instead, and only warn if the file > *actually* changed? That seems to be a rather contrived approach that can still fail in a race situation. There is nothing in the code base that provides digests of complete files, although there are certainly utilities that could be borrowed from for that purpose. (Both encryption and digital signatures are done "by parts" for components carried in Zip files and not on total files. The digest-computation libraries used could probably be reused over complete files.) It would probably be better if actual file-system-level locking against alteration were employed when a file was opened for alteration or replacement. That might be non-trivial because of the way OpenOffice handles file locking, renaming of created files, etc., but it would certainly be better under typical conditions. One could also argue that changing metadata (i.e., what touching the file does at the directory-entry level) qualifies as a change, even though a peculiar one. Is there a particular platform on which this situation is such an annoyance for the client and actually occurs? For accepting patches to accomplish this, there are standard conditions for contributions of code to Apache Projects. For something so impactful, it would be good to have advance agreement at the design level and review of the ramifications. It might be that the project would find the introduction of digest computations to be unacceptable. -- You are receiving this mail because: You are the assignee for the issue.
