From: [EMAIL PROTECTED] Reply-to: [EMAIL PROTECTED] To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=95809 Issue #|95809 Summary|data loss using OOo3 concurrently with another editor |(including OOo2) on the same network
Component|framework Version|OOo 3.0 Platform|All URL|http://www.openoffice.org/issues/show_bug.cgi?id=91015 OS/Version|All Status|UNCONFIRMED Status whiteboard| Keywords| Resolution| Issue type|FEATURE Priority|P1 Subcomponent|code Assigned to|tm Reported by|billrobo ------- Additional comments from [EMAIL PROTECTED] Mon Nov 3 23:01:57 +0000 2008 ------- Data loss through simultaneous editing of network stored files with OOo3 and any other editing application (OOo2, IBM Symphony, MS Office etc). This problem has been caused by the decision to drop system file-locking in OOo3. Example using files a file opened on a cifs-mount (the bug is reproducible with all file formats including ODF and MS Office files): 1) Open a .odt/.doc-file on a client A (Windows or Linux) with OOo3 2) Open the same .odt/.doc-file on a client B with OOo2 or MS Office --> file opens editable (Major problem!) 3) Concurrently edit the document on client A and on client B and save the document. Result: the last save-actions wins, the changes of the first save-action are lost. Notes: * This is a feature request to resolve problems raised in Issue # 91015. * Issues 95528 and 95530 are NOT applicable. They only refer to OOo3 file-locking with other instances of OOo3, not with other editors. * Even for companies that have standardised on OOo it is often not possible to exclusively use OOo (eg a Finance team member may still have a requirement for MS Excel). * When operating in a mixed application environment applications are expected to "play nicely" with each other to be viable - application interoperability is more than just reading each others files. * This is a probable data loss scenario for many Government and medium to large corporate environments and may threaten the viability of OOo3 for these users. Potential options may include: * Enable a "legacy" (OOo2) system file-locking option in OOo3.x * Simultaneously enable both the new OOo3 file-locking and the "legacy" (OOo2) system file-locking option in OOo3.x * Abandon the OOo3 file-locking and revert to the OOo2 style system file-locking option in OOo3.x * Provide a OOo3 fork with OOo2 system file-locking * Continue developing the OOo2 branch in parallel with OOo3 --------------------------------------------------------------------- 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]