> -----Original Message-----
> From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 28 May 2003 5:46 PM
> To: Log4J Developers List
> Subject: Re: cvs commit:
> jakarta-log4j-sandbox/tests/src/java/org/apache/log4j/chainsaw
> CyclicBufferListTest.java
>
>
>
> I am thrilled to see progress on the table model.
>
> As for the CyclicBuffer you could use two cascading cyclic
> buffers. One buffer for storing events as they arrive and a second one
> for the events retained after filtering. The gui table would only use
> the second table to display events. The first one is used only as a
> cache to repopulate the second buffer when the filtering rules
> change. Does it make sense?
We do! ::
class ChainsawCyclicBufferTableModel extends AbstractChainsawTableModel
implements EventContainer {
public static final int DEFAULT_BUFFER_SIZE = 500;
List cyclicBufferList = new CyclicBufferList(DEFAULT_BUFFER_SIZE);
List filteredList = new CyclicBufferList(DEFAULT_BUFFER_SIZE);
(Unless you mean something else...)
cheers,
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
