[ http://issues.apache.org/jira/browse/LOG4NET-11?page=comments#action_62547 ] Göran Roseen commented on LOG4NET-11: -------------------------------------
A workaround - call it ugly or not - would be to log a special message when you want to flush, and then have a trigger on the buffering appender(s)that looks for something specicial in that message. > Add Flush command to API > ------------------------ > > Key: LOG4NET-11 > URL: http://issues.apache.org/jira/browse/LOG4NET-11 > Project: Log4net > Type: New Feature > Components: Core > Versions: 1.2.9 > Environment: From sourceforege - 764025 - Kevin Conroy - kmconroy > Reporter: Nicko Cadell > > While using Buffering is a wonderful way to help improve > performance, I would like the ability to programatically > tell the current ILog object to flush any buffers that > exist on the appenders that I've been logging to so that > I can get any messages that I've sent rather than > waiting for the buffer to fill up. > Thus, one might be able to do the following: > "log.Flush();" > and then any messages sent to that ILog object would > be processed. > Kevin Conroy - kmconroy > ---- > I vote for this one too! > dcazzulino -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira
