JDK-6192552 : Deques
- Type: Enhancement
- Component: core-libs
- Sub-Component: java.util.concurrent
- Affected Version: 5.0
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: windows_2000
- CPU: x86
- Submitted: 2004-11-09
- Updated: 2017-05-16
- Resolved: 2005-09-04
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 6 |
|---|
6 b51Fixed  |
Description
A DESCRIPTION OF THE REQUEST : java.util.concurrent needs a BlockingDeque implementation of BlockingQueue<E>. JUSTIFICATION : See posting from Doug Lea: http://altair.cs.oswego.edu/pipermail/concurrency-interest/2004-November/001101.html The jsr166x Deque interface and its implementations should be extended to BlockingDeque to support blocking LIFO usages. In the mean time, you might want to use the simple LinkedBlockingStack class that I had once written as a classroom example of using ReentrantLock and Condition. It is not generally useful enough to be part of java.util.concurrent, but you can get it from my miscellaneous code page: http://gee.cs.oswego.edu/dl/code/ . You can use it in an Executor by instantiating and sending in one of the messy multiparameter ThreadPoolExecutor constructors. -Doug ###@###.### 2004-11-09 03:50:00 GMT
Comments
|