On 1/9/2010 10:34 AM, Marcello Romani wrote: > Tanstaafl ha scritto: >> On 2010-01-08, O. Felka ([email protected]) wrote: >>> OOo doesn't create a 'temp' file. This file beneath the document is >>> for the file-locking feature. It's not very helpful to create it >>> somewhere in the local environment of the user. >> >> Ok, so how did OOo accomplish this before? The fact is, what I am trying >> to do used to work, and now it doesn't, so something changed and broke >> the previous behavior. >> >> I should be able to edit a document that I have read/write privileges >> for, even if I don't have 'create' privs in that directory. >> > > I think the problem here is how to find a reliable way for multiple > copies of OOo, possibly run by different users on different machines, to > tell each other that a file is in use by one running copy of OOo, and > should be treated "read-only" by others instances of the program > accessing it. > > Of course this problem already has a solution in all network > filesystems, but every OS and every network fs has its own sets of apis > and has differences in its behaviour with respect to locking. > > So I think it's been judged simpler and safer to implement a > platform-agnostic application-specific solution. Think of it as a sort > of OOo-only file lock protocol. > > OOo Gurus pleas correct me if I'm wrong. > > HTH > > Marcello
I dislike all forms of file locking. I find it useless and arbitrary. I'm glad web servers don't engage in file locking, otherwise we'd never be able to update our websites. -- PIT
signature.asc
Description: OpenPGP digital signature
