Good question. The way the server works is that everything that goes on on the server gets logged. I not only want this script to interact with the client but I also want the script to help me "watch" the server which can only be done by watching the logfle. Interacting with the client is just part of the responsiblities of this script.

Another reason is that the client won't be able to interact with the script via the network until he/she requests help from the script. This means that the client needs to type a request (which gets logged) first using a command (defined in the script...like "server_help" or something) and that the script watches for. The fact that the client program has the ability to send udp messages is usually not known by the client user. At least not until the client user makes that request that will then get logged on the server which will then be caught by the logwatcher and in turn react by telling the client user how to talk to the script via the network. Every subsequent request should be made via the clients' ability to send network messages but I could fall back on the log at any time. Redundant? Yes...necessary? I think so.

I hope this all made sense. I started it before work and then finished afterward.

----------
- Jim