> Hello, I am using the example OverbyteIcsThrdSrvV3.dpr plus what happens
is that the wind 
> ClientDisconnect is called before processing the received data, and so the
connection is lost 
> and I can not communicate with the client, it returned me the error 10053
as log below:
>TcpSrv (c) 2005-2010 by François Piette. V3.00
>  TWSocket (c) 1996-2012 Francois Piette V7.87
>  TWSocketServer (c) 1999-2011 F. Piette V7.04 Waiting for clients ...
>Client connected. Remote: Location:
> $ 4,532 ThrdCnt: # 1 There is now 1 clients
>528-533-378 & COD_EVENTO = 00001579 & TPEMISSAO = 0'
>Client disconnecting: Duration: 00:00:21 Error: 10053 ThrdID:
>$ 4,532 ThrdCnt: # 1
>There is now 0 clients connected.

As far as I understand, the client disconnect to fast, without waiting for
the server's answer. So you have to look at the client to understand why it
doesn't wait the response from the server.

Or maybe the client is not supposed to receive a reply from the server, in
which case it is perfectly normal to close the communication on his side.
And of course the server should not send any reply.

If I misunderstood your problem, please try to explain it using other words.
Don't forget to illustrate the protocol in use between client and server.

Embarcadero MVP

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

Reply via email to