Difference between revisions of "Midware TAppServer.OnClientBgException"
Jump to navigation
Jump to search
(Created page with ' Main page -> Midware component reference -> TAppServer -> [[Midware_TAppServer.OnClientBgException | OnC…') |
|||
| Line 6: | Line 6: | ||
== Description == | == Description == | ||
| + | |||
| + | Occurs when an exception is triggered in the background by client socket. | ||
Client communication is handled by a TWSocket descendent component which works in the background. Sometimes, an exception is triggered in the middle of nowhere. Really means the exception is triggered at the lowest message pump level. It is interesting to handle this exception, at least to record it to some log file. It may happend that some exception affect winsock in such a way that no client is able to connect again. You can Stop and Start the server to solve that problem. | Client communication is handled by a TWSocket descendent component which works in the background. Sometimes, an exception is triggered in the middle of nowhere. Really means the exception is triggered at the lowest message pump level. It is interesting to handle this exception, at least to record it to some log file. It may happend that some exception affect winsock in such a way that no client is able to connect again. You can Stop and Start the server to solve that problem. | ||
Revision as of 08:47, 14 May 2011
Main page -> Midware component reference -> TAppServer -> OnClientBgException
Definition
property OnClientBgException: TClientBgException;
Description
Occurs when an exception is triggered in the background by client socket.
Client communication is handled by a TWSocket descendent component which works in the background. Sometimes, an exception is triggered in the middle of nowhere. Really means the exception is triggered at the lowest message pump level. It is interesting to handle this exception, at least to record it to some log file. It may happend that some exception affect winsock in such a way that no client is able to connect again. You can Stop and Start the server to solve that problem.
