Hello, Bender. > 1. my proposal is valid for all FileAppender's and its derivations > (RollingFileAppender, DailyRollingFileAppender) and not only for a > specialized subclass (hence design pattern 'strategy')
I agree. > 2. KeyFileAppender supports only one MDC value, and this is only appended > to the configured filename. With my solution the app developper is free to > build any filename (incl. different path) by using any arbitrary values > taken from where he/she likes. Sure, but is that really needed? > 3. A mechanism for garbage collecting no more used files is a must. That's a must, really. > Some short hints to solve your problem of open files: I thought about threads, too, but I didn't want to go that way. Mostly because of the app server. Am I being too paranoid? Is there another solution? Regards, Leo. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
