socket. If that queue is full a connecting client gets a winsock error
(I forgot the error number).
I think it is the normal 10061 (connection refused). A whell behaving
client should do at least a certain count of retrys.
---
Rgds, Wilfried
http://www.mestdagh.biz
--
To unsubscribe or
Hello Frank,
the client has the event OnChangeState but the server have nothing like
this for the client-connection-lost (not disconnect).
There is no event for a looze connection. If you pull out the network
cable from the client, then both server and client will stay connected,
because to
Fredrik Larsson schrieb:
The TWSocketClientClass is same as TWSocket. I am quite sure that you can
add the onchangestate event just by typecasting to TWSocket.
The following compiles ok...
procedure TForm1.WSocket1ChangeState(Sender: TObject; OldState,
NewState: TSocketState);
begin
//do
Hello Frank,
its right, that have i trying, too. but this recognizes only normal
disconnect and fires an AccessViolation. ;
As I have explained in at least 2 other replys, a disconnect is a packet
sent to the socket. If no packet can be send because for example the
network cable is pulled out,
Hello Frank,
Strange...
I will try to do a test case this weekend for you.
---
Rgds, Wilfried
http://www.mestdagh.biz
Friday, July 1, 2005, 16:20, Frank Wunderlich wrote:
Wilfried Mestdagh schrieb:
Hello Frank,
the client has the event OnChangeState but the server have nothing like
this
Hello Frank,
I've just tweaked the orginal Tcpsrv demo a bit. Dropped a timer on it
and let it send something in intervals, then I pluged off the patch
cable and here is the log:
There is now 1 clients connected.
Received from 192.168.178.200: 'who'
Client disconnecting: 192.168.178.200
Arno Garrels wrote:
Hello Frank,
I've just tweaked the orginal Tcpsrv demo a bit. Dropped a timer on it
and let it send something in intervals, then I pluged off the patch
cable and here is the log:
There is now 1 clients connected.
Received from 192.168.178.200: 'who'
Client
Arno Garrels wrote:
Frank,
You seem to right, for some reason this worked on the server side only.
That's interesting, I will also do some more tests tomorrow.
You are not lucky ;-), the other side took just a rather long time to detect
disconnection from peer, so it is working as expected.
Hello Moacir,
Well, i´m seeing this kind of question so many times... and you people
answering it again and again... nothing agains our´s friends whoe question,
Yes you right. I will save this mails to edit an article in the FAQ !
---
Rgds, Wilfried
http://www.mestdagh.biz
Friday, July 1,
