Hi, On Fri, Jun 8, 2012 at 8:39 AM, Dominik Psenner <[email protected]> wrote: > · the queue size should be configurable
+1 > > · the ThreadPool should be used in favour over a designated worker > Thread no idea becuase I have no clue on .NET, but it sounds like fun :-) > · if the queue is full, it should fallback to synchronous logging, > shouldn’t it? Not sure on this: this would probably impact the application in terms of performance right? Probably this should be configurable to: QUEUE_OVERFLOW_STRATEGY=DISMISS -> throws away the log events QUEUE_OVERFLOW_STRATEGY=SYNC -> goes back to synchronized logging In either case, a warning message should be generated. Another interesting feature would to set a threshhold for the queue. Lets assume it is 100, and 100 messages are in the queue while 150 are allowed, one could get a warning log that the threshhold of 100 is passed. > · queued log events should be processed when the appender gets > disposed +1 Cheers Christian > > > > Cheers, > > Dominik -- http://www.grobmeier.de https://www.timeandbill.de
