[
https://issues.apache.org/jira/browse/LOG4NET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14391132#comment-14391132
]
Stefan Bodewig commented on LOG4NET-407:
----------------------------------------
svn revision 1670747 contains a hybrid of Michael's code, as well as code found
in LOG4NET-344 and the existing AsyncAppender of the example. It should keep
event order for all versions and not lose LoggingEvents when used on .NET >=
4.0.
Documentation is still needed, that's why I'm not closing the ticket
immediately.
> AsyncAppender - better Implementation
> -------------------------------------
>
> Key: LOG4NET-407
> URL: https://issues.apache.org/jira/browse/LOG4NET-407
> Project: Log4net
> Issue Type: Improvement
> Components: Appenders
> Environment: .Net 4.0 and newer
> Reporter: Michael Goldfinger
> Priority: Minor
> Fix For: 1.3.0
>
>
> I checked out the AsyncAppender
> (http://svn.apache.org/viewvc/logging/log4net/trunk/examples/net/2.0/Appenders/SampleAppendersApp/cs/src/Appender/AsyncAppender.cs?view=markup)
> and found some drawbacks.
> * logevents are not logged if the appender close
> * order of logevents got lost
> I created an new implementation that waits for all logevents to be computed
> before close and maintains the order of the events. If the application
> process got killed the logevents are lost too but in any other case the loss
> of logevents could be prevented. The drawback of my implementation is that
> the TLP is requred so .NET 2.0 is not supported.
> I could not find the place to contribute so I created this ticket. I hope
> it's useful.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
