8 Jan
2009
8 Jan
'09
12:50 p.m.
On Thu, Jan 8, 2009 at 6:36 AM, Cristiano Paris
This avoids the possibility of having an unwanted/unknown behavior from the run-time stack (for example, having the web server returning a generic 500 Internal Server error report, filled with every sort of goods a cracker would be happy for).
So the information should be written to the log rather than the browser, at least in production, but there's no reason not to catch the exception.
Cristiano
--Max