Frank Wunderlich wrote: >>>> You could check a 'last alive' time stamp stored in your client class. >>>> Cleanup the client after a timeout has elapsed. Use a single Timer to >>>> check all clients actually in the list in intervals. >>>> >>>> Arno Garrels > is there a procedure to send something direct to the clients or do i need > a 2nd TWsocket, getting the client adress and send to that?
Why would you need that?? Of course you could make the client a listening server too, but then you don't know whether your server is reachable or not ;-) It's very easy, if a client does not request something within a given period of time just kill him. You could send some kind of NOOP messages to the server in intervals to keep client connections alive. If the client isn't reachable when you sent back a reply to a request an error lets you know that the client isn't active. Arno Garrels > frank > > -- > Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis > ++ Jetzt anmelden & testen ++ http://www.gmx.net/de/go/promail ++ -- 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
