These sound like good ideas.
Not sure why you need two TimeoutWrappers though, as
you are only trapping the remove() aren't you?
Stephen
--- James Carman [EMAIL PROTECTED] wrote:
Based on my response to Sandy McArthur about using
Buffers to implements
Commons Pool, I started digging around
No, you'd need to override add also, so you'd know when to fire
notify()/notifyAll(). Correct?
-Original Message-
From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 7:40 AM
To: Jakarta Commons Developers List
Subject: Re: [collections] New Buffer
: Stephen Colebourne [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 7:40 AM
To: Jakarta Commons Developers List
Subject: Re: [collections] New Buffer Wrapper Classes...
These sound like good ideas.
Not sure why you need two TimeoutWrappers though, as
you are only trapping the remove
Based on my response to Sandy McArthur about using Buffers to implements
Commons Pool, I started digging around the API. I came up with a couple of
ideas:
1. A BoundedBuffer wrapper/decorator class, which basically enforces a
maximum size of the enclosed buffer.
2. A TimeoutBuffer
