commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37473] - [collections] Implement a BoundedBuffer class
Date Thu, 24 Nov 2005 22:52:51 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=37473>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=37473





------- Additional Comments From james@carmanconsulting.com  2005-11-24 23:52 -------
The class doesn't necessarily block, so I don't think it should have "blocking"
in the name.  If you supply a negative number (the default) for the timeout
value, it doesn't wait at all, but immediately throws a BufferOverflowException.

The use case is so that any buffer implementation can be made to have a maximum
size.  That way, we don't need to have classes called BoundedFifoBuffer and the
like.  We could just have FifoBuffer (which would by default be unbounded).  If
you want it to be bounded, just wrap it with a BoundedBuffer.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message