On Tuesday 10 April 2007 16:49, Robert Varttinen wrote: > Hi, > An enterprise setting is just what I'm into in my current project. I'd like > a variant of 2, i.e. not really buffer events, but rather have them revert > to soemthing more basic, like writing to the console as a last resort. I do > not think buffering should be done for a prolonged time in order to avoid > memory related problems. It could, however, be done briefely if the the > logging capability is temporarily unable to write events to a specified > log. Guess there could some config settings for this behaviour ...
Exactly my thoughts as well. My implementation is now settable to up to 1000 events buffer size and defaults to 25. But perhaps a time limit of 1 minute or something would be a smart choice. In any event, source is available at https://scm.ops4j.org/repos/ops4j/projects/pax/logging, and steadily pushing forward to a 1.0 final release which I intend to be TCK compliant. The other main feature is of course full legacy API support; Log4J, commons-logging, SLF4J, Avalon Logging, KF Log, JDK logging Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug _______________________________________________ OSGi Developer Mail List [email protected] http://www2.osgi.org/mailman/listinfo/osgi-dev
