posted 16 years ago
Just to elaborate slightly, it means you tried to send some data to the client and the client had already closed the connection.
IF you do all your processing before sending the response to the client it is unlikely to be an issue. If you mix business logic and presentation so that you are processing and responding at the same time you may have the Exception force you to jump out of your code when you're not expecting it.
Also, I'm assuming that the response sent to the client is not important, but this is not always the case. If your response should be included in the 'transaction' eg it includes a receipt number or the receipt of the data is important (ie they have to download the entire response) then you may need to manage this behaviour.
Back to my original suggestion: being aware that this can occur is important, but usually you are able to ignore it.