> I will be writing both server and client softwares. No need for a > web server.
In which case the server should only ever listen for TCP connections from clients, which open the connection and send a hello packet once a minute to prove they are alive, expecting a response so they know the server is alive. Your can start with my TMagIpLog component, which can be configured as the client or server, and handles all the opening, retrying and closing of connections, allowing lines of text (ie your protocol) to be send back and forward. http://www.magsys.co.uk/delphi/magics.asp You only need to add a couple of events in your code and it should all be working in an hour. For my old bus project, we had three 'activity servers' that the client PCs contacted in rotation in case of hardware or other problems, and we had a fall back of a UDP listener on the client that listened to UDP broadcasts from the server to force all the clients to immediately call home, and a few others things. Our protocol document was about 50 pages with 40 different commands or something, quite complicated, things like retrieving CCTV from the buses. Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
