Arno Garrels schrieb:
Frank Wunderlich wrote:
Hallo Arno,
am Freitag, 1. Juli 2005, 18:52:25 hast du geschrieben:
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 disconnecting: 192.168.178.200 Duration: 00:01:08Error: 10053
There is now 0 clients connected.
It is exactly working as we told you.
Arno Garrels
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
where did you generate that log (the line with errorcode). is this the
onclientdisconnect?
Yes, take a look at Tcpsrv demo, I only added "+ 'Error: ' + IntToStr(Error)"
how do you send (the same way i do?)?
Yes, iterating thru the list of clients sending a string.
Arno Garrels
it does really not work for...here the changes in the tcpsvr-demo:
procedure TTcpSrvForm.Timer1Timer(Sender: TObject);
var i:integer;
begin
for i:=0 to WSocketServer1.ClientCount-1 do
begin
WSocketServer1.Client[i].SendStr('Blah'+#13#10);
end;
end;
procedure TTcpSrvForm.WSocketServer1ClientDisconnect(
Sender : TObject;
Client : TWSocketClient;
Error : Word);
begin
with Client as TTcpSrvClient do begin
Display('Client disconnecting: ' + PeerAddr + ' ' +
'Duration: ' + FormatDateTime('hh:nn:ss',
Now - ConnectTime)+' Error: '+IntToStr(Error));
Display('There is now ' +
IntToStr(TWSocketServer(Sender).ClientCount - 1) +
' clients connected.');
end;
end;
the server does not fire the onclientdisconnect in my application...i
don't know why...
what have you done in another way?
Greets frank
--
To unsubscribe or change your settings for TWSocket mailing list
please goto http://www.elists.org/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be
