Uploaded image for project: 'Log4net'
  1. Log4net
  2. LOG4NET-232

Use ReaderWriterLockSlim instead of ReaderWriterLock.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Fixed
    • 1.2.10
    • 1.2.12
    • None
    • None
    • Any

    Description

      ReaderWriterLock should be replaced with ReaderWriterLockSlim according to Microsoft for performance and simplification reasons.

      MSDN: http://msdn.microsoft.com/en-us/library/system.threading.readerwriterlock.aspx

      The .NET Framework has two reader-writer locks, ReaderWriterLockSlim and ReaderWriterLock. ReaderWriterLockSlim is recommended for all new development. ReaderWriterLockSlim is similar to ReaderWriterLock, but it has simplified rules for recursion and for upgrading and downgrading lock state. ReaderWriterLockSlim avoids many cases of potential deadlock. In addition, the performance of ReaderWriterLockSlim is significantly better than ReaderWriterLock.

      Attachments

        Issue Links

          depends upon

          New Feature - A new feature of the product, which has yet to be developed. LOG4NET-176 Buildable with VS 2008 and .NET FW 3.5

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            People

              nachbarslumpi Dominik Psenner
              aronweiler Aron Weiler
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: