tag:blogger.com,1999:blog-11485813.post1730301133956518979..comments2024-02-03T09:45:28.960+05:30Comments on Enlightened ... There are no special effects.: OOP - POOSridharhttp://www.blogger.com/profile/08903225715273678219noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-11485813.post-85093551605200543722007-03-07T19:02:00.000+05:302007-03-07T19:02:00.000+05:30Logging should be as least intrusive as possible. ...Logging should be as least intrusive as possible. You would have probably fixed some the exceptional cases of logging (like path not found) in your testing or when you smoke tested the app on production. Exceptions like disk full caused by logging alone is bad, often implies that logs are not cleared and/or unwanted stuff gets logged.<BR/><BR/>Well, the idea is logging should not affect the normal functioning of the application.Sridharhttps://www.blogger.com/profile/08903225715273678219noreply@blogger.comtag:blogger.com,1999:blog-11485813.post-12803333411703088082007-03-07T18:56:00.000+05:302007-03-07T18:56:00.000+05:30That was a simple logging mechanism I don't think ...That was a simple logging mechanism I don't think it can get simpler. <BR/><BR/>On your point that the logging funtion should not throw any exception, if the logging is happening to a file/table, then exceptions (like FileNotFound, db-related Exceptions) do come into the picture, right ?Anonymousnoreply@blogger.com