PS> Hmmm, what's this client/servet thing? Could you 
 PS> explain? File locking I know

In this context -- the client code (which does no file i/o) would send a
message to the server, like "read next message",  or "write
message". The server,  being a separate process (perhaps on a
different PC) would process these messages from all clients.  Since the
server is the only process that has any message files open,  it need not
use any locking at all.  This is _very_ efficient across a network, when
file locking is the other alternative.

Server processes usually have no (or very little) user interface.  For
example,  the game "quake" is client/server.  The server (not
having a user interface) is very portable,  and has been ported to many
OS's.

The quake server is kinda hidden for the normal stand-alone user,  but it
is how the multi-player game works.


--- Maximus/2 3.00