Greetings bear,

In addition to the wonderful responses you've already received, I'd add that it would be a good idea to have a fatalsToEmail and fatalsToBrowser routine. In a recent project I've been playing around with, I used the set_message with CGI::Carp fatalsToBrowser to send myself an email and display a "nice" error page to the user. Of course, the "nice" error page tells the user very little other than an apology and some contact information. For a future version, I was thinking about providing the user some sort of automated "summary" information about the particular error. Any such information should be vague enough as to not provide any crackers with any useful information.

Oh, and as I'm sure someone has noted before, always make sure you turn off the "report full text of the error message to browser" feature before you launch go into public enviornment.

gryphon
code('Perl') || die;