Howdy, That doesn't seem like it'd be difficult to write. Alternatively, we could port your existing MemoryTarget into a log4j Appender fairly easily I bet...
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Berin Loritsch [mailto:[EMAIL PROTECTED] >Sent: Tuesday, June 17, 2003 4:00 PM >To: Log4J Developers List >Subject: Re: Official Collaboration? > >Ceki Gülcü wrote: >> At 02:53 PM 6/17/2003 -0400, Berin Loritsch wrote: >> >> We don't have Memory, I mean a MemoryAppender. What is the use case >> for a MemoryAppender? >> >> Actually, the SMTPAppender is based on a cyclic buffer that sends off >> an email when a triggering event occurs. Still that is quite different >> than LogKit's MemoryTarget. > > >:) > > From the JavaDoc on it: > > * Output LogEvents into an buffer in memory. > * At a later stage these LogEvents can be forwarded or > * pushed to another target. This pushing is triggered > * when buffer is full, the priority of a LogEvent reaches a threshold > * or when another class calls the push method. > * > * This is based on specification of MemoryHandler in Logging JSR47. > >I don't recall it being used much--but there are other users besides >me. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]