> Audit will require transactions, which is to say that the calling code needs >to know if the Audit message has been persisted or not before it can >continue.
>From the log4net FAQ on the Apache site: "Is log4net a reliable logging system?" "No. log4net is not reliable. It is a best-effort and fail-stop logging system." I don't love the use of the word "reliable" as everyone wants to use something that's reliable, but the point of the statement is, IF something fails in log4net it was designed to NOT stop the application from running. Now, you could probably rework some of the plumbing, but I think log4net is orthogonal to an audit log. Having said that, you'll have to pry log4net out of my cold dead hands. :) -Walden -- Walden H Leverich III Tech Software (516) 627-3800 x3051 [EMAIL PROTECTED] http://www.TechSoftInc.com Quiquid latine dictum sit altum viditur. (Whatever is said in Latin seems profound.) -----Original Message----- From: shaeney [mailto:[EMAIL PROTECTED] Sent: Monday, October 22, 2007 6:14 AM To: [email protected] Subject: Newbie: Log4Net or MS Logging Application Block? Hello all, I have been asked to compare the Log4Net library with the Microsoft patterns & practices Logging Application Block. I have searched this forum but can't find anyone who has asked this question previously. I would have thought this is a common topic. Does anyone know if this type of side-by-side comparison has been done? I know that both are very extensible, but I am interested in comparing the core deliverables. In particular, I am interested in using either for both Logging and Auditing purposes. Audit will require transactions, which is to say that the calling code needs to know if the Audit message has been persisted or not before it can continue. Cheers, Steve -- View this message in context: http://www.nabble.com/Newbie%3A-Log4Net-or-MS-Logging-Application-Block- -tf4669838.html#a13339938 Sent from the Log4net - Users mailing list archive at Nabble.com.
