Yes, I guess that's possible. This is how it works at the moment.
I have an array of records. Each record contains a string and an integer. The string is used to hold the incoming data and integer hold the timeout value that counts down. As data arrives it is added to the string associated with the correct client and the timeout is reset to 20 seconds. Periodically I check each of the strings in the array to see if <mos> and </mos> exist. If this is the case the message is extracted from the string and processed. The timeout is now turned off. Occasionally I get issues with data appearing to be corrupt. Investigations are continuing, but the origin of this e-mail trail was to establish if it worth my while changing from Delphi TServerSocket to the ICS server component. Is the ICS component known to be better in whatever respect or is it just an equally good alternative. Graham -----Original Message----- From: TWSocket [mailto:twsocket-boun...@lists.elists.org] On Behalf Of François Piette Sent: 09 October 2013 17:21 To: 'ICS support mailing' Subject: Re: [twsocket] Delphi TServerSocket vs ICS equivalent > The data is enclosed with a standard tag format. In this case it is <mos>.....</mos>, so I know when > I have received a complete message So you have a delimiter which is "</mos>". It could be sed for TWSocket LineMode. Note that you cannot have embedded messages in messages. -- francois.pie...@overbyte.be Embarcadero MVP http://www.overbyte.be http://francois-piette.blogspot.com -- 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 -- 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