I have been playing around with the logging facility of Poco. I notice something which is not a problem, but wonder if there is an easy way around it that I have not noticed.
If I am using a SplitterChannel to route log messages to a ConsoleChannel and a FileChannel. Just for the fun of it I externally "locked" the log file so the FileChannel would not be able to open the file for writing. As expected, an exception was thrown and my application died.
Is there an easy way (without modifying the existing library) to change this behavior without wrapping the the calls to log() in a try-catch. In other words, a way to configure the FileChannel to not throw an exception on failure. The "locked" file is just an example. There are a number of things which could cause an exception while logging I suppose.
I can imagine the logging channel classes supporting some type of "NoException" (sorry for the name, just an example (:smile:) ) property. That way if someone is using the LoggingConfigurator, they could keep a particular channel from killing the application if it were to fail.