in reply to Error Handling and Logging for Object-Oriented Perl Application

If you use Apache as an example there are a two logs but only one of them is called error.log which hints at the heirarchy. You may want to log a variety of things, only one of which is errors.

To my mind log is a base class that error inherits from/uses and adds the email_admin() lie_to_user() and die_if_realy_bad() methods to. You may of course want to add more mundane methods like roll_back() retry() and recover() but that is up to you....

Time is a vital element (who changed what at 10:03:42 that broke the widget module) plus whatever else seem relevant. Relevant should be a topic of discussion. It is obviously better to log too much (you can filter) than too little (use ESP?) You can always rotate the logs if they get to big but you can never recover electrons that have been lost.

cheers

tachyon

s&&rsenoyhcatreve&&&s&n.+t&"$'$`$\"$\&"&ee&&y&srve&&d&&print

  • Comment on Re: Error Handling and Logging for Object-Oriented Perl Application