> Why not just give the option of sending an alert > instead of closing the app with a fatal error?
The app close only because you don't handle the exception. You can handle the exception as you like. It is not the component which has to display an alert, it is your application. Contribute to the SSL Effort. Visit http://www.overbyte.be/eng/ssl.html -- [EMAIL PROTECTED] Author of ICS (Internet Component Suite, freeware) Author of MidWare (Multi-tier framework, freeware) http://www.overbyte.be ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <twsocket@elists.org> Sent: Thursday, March 27, 2008 8:41 AM Subject: [twsocket] THttpCli exception errors > Why is ICS written to trigger an exception error upon events such as an > internal server error, or when a connection request is aborted in the > middle of receiving data from the server? The code I am referring to is > this: > > if (FStatusCode >= 400) and (FStatusCode <> 401) and (FStatusCode <> 407) > then > raise EHttpException.Create(FReasonPhrase, FStatusCode); > > Why not just give the option of sending an alert instead of closing the > app with a fatal error? > > -- > Want an e-mail address like mine? > Get a free e-mail account today at www.mail.com! > > -- > To unsubscribe or change your settings for TWSocket mailing list > please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket > Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
