In TWSocketServer, when an exception occur at the time a client is connecting, maybe in your own event handler code (for example in OnClientConnect event), a BgException is triggered. If you have no handler for this event, the listening socket is aborted (closed) and the exception is silently ignored. If you have a handler, you have the choice of not aborting the socket and keep it listening. Note that depending on what the exception was and where it occured, it is possible that the component is in a strange state. I think it is better to let the abort occur to have the component back to a known state (closed) and make it listen again a few moment later, probably by posting a custom message to the form and from the corressponding event handler making the socket listening again.
-- Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] http://www.overbyte.be ----- Original Message ----- From: "A.Shekar " <[EMAIL PROTECTED]> To: <firstname.lastname@example.org> Sent: Saturday, September 10, 2005 7:14 AM Subject: Re: [twsocket] WSocketServer stops listening > Hi Wilfried, > The normal load is 40-60%. In Server BGException i set CanClose := > False. Other info i can check on monday morning. > > regards > Shekar > > -- > 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 -- 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