Hello David, > Is that the correct logic for it all?
yes it is correct. > I have tried a number of different ways of doing this, but each way > doesn't seem to have reliable communications. Should be very reliable. If you can provide some more detail of what the problem is, then we all very glad to help. --- Rgds, Wilfried http://www.mestdagh.biz Tuesday, September 6, 2005, 10:55, David Lewis wrote: > I've been trying to sort out a stable client/server connection with ICS > but I'm having a few difficulties, and I'm thinking that maybe my > understanding of how it works may be a little wrong. > Initially, I am building one application which can act as a client & > server, and put one on the remote machine and for them to talk to each > other. I set the IP addresses & ports differently on each. > What I have: > 1 x TWSocket for sending messages to a remote server > 1 x TWSocketServer for receiving messages from a remote system > The TWSocketServer creates a new TTcpSrvClient for each incoming connection. > Now, I believe that it works like this: > To send a message, I use TWSocket component. > The remote machine then sees an incoming connection in TWSocketServer > and creates a TTcpSrvClient for that connection. > The TTcpSrvClient then receives the message and a reply can be sent back > through this component. > This reply is then picked up back in the TWSocket that sent it. > When the TWSocket closes the connection, the TTcpSrvClient is > automatically deleted and things go back to square one. > Is that the correct logic for it all? > I have tried a number of different ways of doing this, but each way > doesn't seem to have reliable communications. > I've looked at the examples for these components, and this way is my > understanding of them, but I want to be sure hence my posting here, > cause something is still not quite right. > Thanks, > Dave -- To unsubscribe or change your settings for TWSocket mailing list please goto http://www.elists.org/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
