Hi,

LOG4NET-164 introduced a new locking strategy for FileAppender which
technically uses a System.Threading.Mutex with a name built from the log
file's name.  This should allow separate processes to share a log file
without repeatedly opening and closing it.

The main remaining issue is its name (apart from docs which will follow
once the name is settled).  Right now it is called MutexLock but that
may not convey to users what this actually does - they'd need to know
what a Mutex is in the first place.

I'm notoriously bad at names so I'm asking here now.  Names suggested in
the JIRA ticket are "InterProcessLock", "SystemWideLock" and
"GlobalLock".

Stefan

Reply via email to