Here’s the setup:
... A network.
... One plaintext file on the server.
... One fixed client who can write to that file.
... Several clients who can read it.
Because only one client is allowed (enforced by the program) to write to the file, I do not have the program put a write lock on the file when writing.
I do not have it put a read lock on it either.
Question (really ignorant, but I’m not really a programmer):
... Is it always safe for a reader client to read the file, including when the writer client is writing to it?
By “safe” I mean that the reader gets the file contents uncorrupted and entire, either what it was before the write or afterwards, it doesn’t matter which.
(At present I’m using VB on this, but presumably the answer for PBWin is the same. Also, eventually I’m converting to PBWin.)
... A network.
... One plaintext file on the server.
... One fixed client who can write to that file.
... Several clients who can read it.
Because only one client is allowed (enforced by the program) to write to the file, I do not have the program put a write lock on the file when writing.
I do not have it put a read lock on it either.
Question (really ignorant, but I’m not really a programmer):
... Is it always safe for a reader client to read the file, including when the writer client is writing to it?
By “safe” I mean that the reader gets the file contents uncorrupted and entire, either what it was before the write or afterwards, it doesn’t matter which.
(At present I’m using VB on this, but presumably the answer for PBWin is the same. Also, eventually I’m converting to PBWin.)
Comment