James Finnall wrote:
I have seen several replies to this question. But none seem to address the original issue of the creation of the file itself. It has been my long understanding that file locking semantics are _NOT_ part of any data application program to start with. So any file for the purpose of file locking is totally unwarranted and undesirable. It is the responsibility of the OS that is providing the file share service to adequately protect the file from operations that could cause any form of data loss or undesirable results.
A nice idea. But given the way it's been done, I suspect the developers had networked machines in mind. I'm pretty sure there's no locking mechanism that will work across windows, mac, and assorted flavours of un*x on a network - other than a crude lockfile. It would probably have been better though if the file had been named something different.
My two cents worth. James
-- Mike Scott Harlow Essex England.(mike -a-t- scottsonline.org.uk) (Processing of this email by 3rd parties in relation to advertising services is forbidden.) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
