To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=85794





------- Additional comments from [EMAIL PROTECTED] Fri Jun 13 12:40:45 +0000 
2008 -------
I tested the filelocking implementation of OOo3 (300m2 Rev 9301) on Windows and
found the following bugs which lead to data loss:

No File locking for doc-files shared via samba-share:
1) Open a .doc-file that is hosted on a samba-share on Windows-host A
2) Open the same .doc-file on Windows-host B --> file opens editable (!!!BUG!!!)
3) edit the document on host A, save and close the document
4) edit the document on host B, save and close the document

result: changes done in 3) are lost! The file-locking for .doc-Files on windows
is broken.

Another issue affects the file-locking in a heterogenous environment with a file
shared via samba-share, opened in OOo3 on Windows and in OOo2 on linux with
cifs-mount (the bug is reproducible with .doc AND .odt-files):
1) Open a .odt/.doc-file on a Windows host A with OOo3
2) Open the same .odt/.doc-file on a linux-client B with OOo2 --> file opens
editable (!!!BUG!!!)
3) edit the document on host A and B and save the document.

result: the last save-actions wins, the changes of the first save-action are 
lost.

Please add these two usecases to your testcase and test again! Please notice
that these usecases are real-world usecases which will occur regulary in our
heterogenous environment while introducing OOo3.

In this point the file-locking implementation of OOo2 is better than OOo3 as
there is no data loss with OOo2 in the same usecases. I think this would be a
blocker for us not to use 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]

Reply via email to