 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
Guest
|
Posted: Mon Sep 18, 2006 8:11 am Post subject: TIdTcpClient remains connected when buffer is not empty |
|
|
Hi all,
something is wrong with the TIdTcpClient. After the server is closed,
it raises an exception (correctly) but it remains connected (at least
it thinks it is connected) when the read buffer is not empty.
Example:
- open server
- connect client
- client reads the socket, EOL character is 'b'
- server sends 'abcd'
- client reads 'a', 'b' is ignored, 'c' and 'd' remains in the buffer
- close server
- client raises the exception, but it remains connected
If the EOL is 'd', it works correctly - after the exception it is
disconnected.
Am I doing something wrong? Can I flush the buffer somehow?
I tried it with Indy 10.1.5.
--
Scappy |
|
| Back to top |
|
 |
Riki Wiki Guest
|
Posted: Mon Sep 18, 2006 11:45 pm Post subject: Re: TIdTcpClient remains connected when buffer is not empty |
|
|
On 18 Sep 2006 00:38:31 -0700, tblaho (AT) identcode (DOT) cz wrote:
| Quote: | Am I doing something wrong?
|
Hoi
You need to repost your message on the Borland news server to make
everybody see it and possibly answer your message.
How to post to Delphi newsgroups:
<http://delphi.wikia.com/wiki/Delphi_Newsgroups> |
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|