I had a similar problem when converting to XE2 from Delphi7 - my TwSocket component was designed to send a header string containing the length of the data to follow, and then I would read that bit to get the actual data - and then process it - but with XE2 being unicode aware - suddenly I had extra characters in the actual transmitted message - so the counter at the beginning of the data did not match the actual data - and therefore there was still stuff to receive (still in the buffer) so it hung the client up.
Regards Brian On Wed, Feb 1, 2012 at 4:20 AM, <mfisc...@bfe.tv> wrote: > > Hi, > i am using the Standard TWSocket in a Server and round about 5 Clients > without > LineMode. After a Client is connected to the Server, the Client starts > immediately to send text messages. After some sort of filtering the > messages > are broadcasted to a subset of all connected Clients. If i start the sever > and > 5 clients through a script on a single Windows 7 PC the following error > occurs: After a few Bytes are exchanged one or two of the clients no longer > call the > callback function for OnDataAvailable. The ServerSocket and and the > ClientSocket stay in state > wsConnected. If i look at WireShark the Data is still transmitted from > Server > to Client. > If the ClientSocket is closed, the callback for OnDataAvailable is > triggered > and the missing > Bytes are "received". > Any idea in which direction my problem could be located? > Thanks, > M. Fischer > -- > 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