Remoting appender: If the application goes down that's finally persisting the log events, the logging is down too.
InterProcessLock / MutexLock: Since every application persists the log events by itself, the logging survives as long as the application is "alive". _____ From: Ron Grabowski [mailto:rongrabow...@yahoo.com] Sent: Wednesday, September 14, 2011 12:44 AM To: Log4NET Dev Subject: Re: Name for MutexLock? Can you share a config snippet showing how to use the RemotingAppender like you've described? What happens when one of the apps goes down? I envision the InterProcessLock as a locking model used between two low/medium chatty apps that want to write to the same file that may or may not be running at the same time.
