Think about Loose Coupling | |
PerlMonks |
Re: Defensive Programming and Audit Trailsby mjeaton (Hermit) |
on Aug 06, 2002 at 13:33 UTC ( [id://188014]=note: print w/replies, xml ) | Need Help?? |
These are all things that I point out to my classes as much as I can. I try to explain how much help they can be, and I certainly hope that my students take my advice and use some type of logging in their applications. Logging is something I add to pretty much any non-trivial program. Since most of my work falls into the non-Perl category, I've had to come up with different solutions over the years. One place I worked had the coolest logging framework that I've seen. Each client (mostly VB, but some C) referenced a dll that exposed methods like Trace, Status, Alert and CriticalAlert. Trace was for things that a developer wanted to see like SQL statements, variable info, etc. Since our support people weren't developers, they would see all the status messages -- startup, shutdown, records inserted, updated and deleted. If an alert log was written, an email would be generated and a CriticalAlert log would generate a page to the on-call support person.
In Section
Meditations
|
|