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





------- Additional comments from [EMAIL PROTECTED] Wed Sep 28 23:20:29 -0700 
2005 -------
@sb: hmm, strange: I thought I'd replied to your latest comments, but there is
nothing in the issue :(.  So here we go again:

- "Correct me if I am wrong, but as far as I know, locks are removed as soon as
any file descriptor on the same file is closed, and that is a general design
"feature" of fcntl(F_SETLK), irrespective of NFS." 

I don't remember the details (so you are probably right on them). However, the
result is the same - we actively need to make sure that a file get's opened only
once at a time.

- "Compare-and-overwrite would have to be an atomic
operation then, which it is not.  Thus, your proposed approach #6 IMO gives a
false sense of security."

The point I was trying to make is that the feedback IMHO needs to arise at the
time the user _saves_ the document, not when (s)he opens it (which potentially
could be days earlier). To make this more atomic, the algorithm could work like:

save operation: try locking the file and warn if that fails (cancel y/n) -
compare modification time and warn if that fails  (cancel y/n) - overwrite the
document.

I could even imagine that the modification time gets checked each time the
window contain the visualization of the document receives the focus.



---------------------------------------------------------------------
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