http://bugzilla.slf4j.org/show_bug.cgi?id=211
--- Comment #3 from Ondrej Zizka <[email protected]> 2011-02-09 20:55:37 CET --- Here's a related discussion from Apache Log4j's Bugzilla: Olivier Dupuy "I totally aggree with the flushing being tied to the level of the event (as in 28647). This totally makes sense and would be good to have it in the default log 4J." ... I would add one more use case: Say, the underlying logging may have buffering enabled. The application, still above logging mechanism abstraction, is aware of this, so needs to flush logs at certain point; e.g. when the developer needs to see the state after some action; or when there are more sources logging to the same stream. https://issues.apache.org/bugzilla/show_bug.cgi?id=41670 -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ slf4j-dev mailing list [email protected] http://qos.ch/mailman/listinfo/slf4j-dev
