🚀 go-pugleaf

"Hans Galema" <dontusethis@dontusethis.nl> wrote in message
news:3f8ced2e@newsgroups.borland.com...
> Dennis Jones wrote:
>
> > At first I thought specifying the appropriate file sharing modes would
work,
> > but then I realized that that would only work to block access to the
file
> > for other processes running on the SAME machine.
>
> Is that true ? Hard to believe. If you lock the file (and get the lock)
> the access will to blocked by the os on the shared machine for others

Well, I don't know for sure, I haven't actually tried it yet -- just trying
to get suggestions before I start work on it.  I was assuming that any kind
of file locking being done by the OS would have to be done with some sort of
internal kernel object, which of course, no other machine would know about.

>
> > Any additional ideas would be welcome.
>
> Isn't appending to a file with fwrite() an atomic process ?

No, I don't think so, not even for multiple processes/threads on the same
machine.

>
> Every client could open the file once for a whole session.
> You do not have to lock. After fwrite() you could flush.

I would be very suspicous of code that did that.

> That would be all.

Unfortunately, I think there is a lot more to it than that.

- Dennis