You are viewing a plain text version of this content. The canonical link for it is here.

Posted to log4net-dev@logging.apache.org by "Stefan Bodewig (JIRA)" <ji...@apache.org> on 2011/09/06 11:52:09 UTC

[jira] [Updated] (LOG4NET-232) Use ReaderWriterLockSlim instead of ReaderWriterLock.

     [ https://issues.apache.org/jira/browse/LOG4NET-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stefan Bodewig updated LOG4NET-232:
-----------------------------------

    Fix Version/s: 3.5

> Use ReaderWriterLockSlim instead of ReaderWriterLock.
> -----------------------------------------------------
>
>                 Key: LOG4NET-232
>                 URL: https://issues.apache.org/jira/browse/LOG4NET-232
>             Project: Log4net
>          Issue Type: Improvement
>    Affects Versions: 1.2.10
>         Environment: Any
>            Reporter: Aron Weiler
>            Priority: Minor
>             Fix For: 3.5
>
>
> 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. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira