10 |
by <a href="http://gee.cs.oswego.edu/dl">Doug Lea</a> |
by <a href="http://gee.cs.oswego.edu/dl">Doug Lea</a> |
11 |
<p> |
<p> |
12 |
|
|
13 |
This is an updated version of the specification submitted for JCP |
This is maintenance repository of JSR166 specifications. For further |
14 |
Community Draft review. To check for further updates, access a |
information, go to: <A |
|
preliminary prototype release of main functionality, or join a mailing |
|
|
list discussing this JSR, go to: <A |
|
15 |
HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> |
HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> |
16 |
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A> |
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A>. |
|
. <p> |
|
17 |
|
|
18 |
<em> <b>Disclaimer</b>. The prototype implementation is experimental |
<p><em>Note: The javadocs here do <em>not</em> include pre-existing |
19 |
code developed as part of JCP JSR-166 is made available to the |
java classes (for example <tt>java.lang.Thread</tt>) that were changed |
20 |
developer community for use as-is. It is not a supported product. Use |
as part of the JSR166 spec. On the other hand, the javadocs here do |
21 |
it at your own risk. The specification, language and implementation |
include some existing java.util Collection interfaces and classes that |
22 |
are subject to change as a result of your feedback. Because these |
are not part of the spec, but are included because some new methods |
23 |
features have not yet been approved for addition to the Java language, |
implement or inherit from their specifications. |
24 |
there is no schedule for their inclusion in a product. </em> |
</em> |
|
|
|
|
<p> <em> <b>Disclaimer</b>. This draft specification was produced |
|
|
using JDK1.4 tools plus some preprocessing. The resulting javadocs do |
|
|
not yet correctly render other planned JDK1.5 constructs on which |
|
|
JSR-166 relies, most notably the use of generic types. We are |
|
|
releasing this version now (before the availability of JDK1.5-based |
|
|
tools) because, even though they are misformatted and sometimes lack |
|
|
proper cross-referencing, they otherwise convey the intended |
|
|
specifications. </em> |
|
25 |
|
|
26 |
<p> JSR-166 introduces package <tt>java.util.concurrent</tt> |
<p>JSR-166 introduces package <tt>java.util.concurrent</tt> |
27 |
containing utility classes commonly useful in concurrent |
containing utility classes commonly useful in concurrent |
28 |
programming. Like package <tt>java.util</tt>, it includes a few small |
programming. Like package <tt>java.util</tt>, it includes a few small |
29 |
standardized extensible frameworks, as well as some classes that |
standardized extensible frameworks, as well as other classes that |
30 |
provide useful functionality and are otherwise tedious or difficult to |
provide useful functionality and are otherwise tedious or difficult to |
31 |
implement. |
implement. |
32 |
|
|
33 |
<p>JSR-166 focusses on breadth, providing critical functionality |
<p>JSR-166 focuses on breadth, providing critical functionality |
34 |
useful across a wide range of concurrent programming styles and |
useful across a wide range of concurrent programming styles and |
35 |
applications, ranging from low-level atomic operations, to |
applications, ranging from low-level atomic operations, to |
36 |
customizable locks and synchronization aids, to various concurrent |
customizable locks and synchronization aids, to various concurrent |
38 |
pools. This diversity reflects the range of contexts in which |
pools. This diversity reflects the range of contexts in which |
39 |
developers of concurrent programs have been found to require or desire |
developers of concurrent programs have been found to require or desire |
40 |
support not previously available in J2SE, which also keeping the |
support not previously available in J2SE, which also keeping the |
41 |
resulting package small; providing only that minimial support for |
resulting package small; providing only functionality that has been |
42 |
which it makes sense to standardize. |
found to be worthwhile to standardize. |
43 |
|
|
44 |
<p>Descriptions and brief motivations for the main components may be |
<p>Descriptions and brief motivations for the main components may be |
45 |
found in the associated package documentation. JSR-166 also includes |
found in the associated package documentation. JSR-166 also includes |
60 |
class: |
class: |
61 |
<ul> |
<ul> |
62 |
<li> It now allows per-thread installation of handlers for uncaught |
<li> It now allows per-thread installation of handlers for uncaught |
63 |
exceptions. Ths optionally disassociates handlers from ThreadGroups, |
exceptions. This optionally disassociates handlers from ThreadGroups, |
64 |
which has proven to be too inflexible. (Note that the combination of |
which has proven to be too inflexible. (Note that the combination of |
65 |
features in JSR-166 make ThreadGroups even less likely to be used in |
features in JSR-166 make ThreadGroups even less likely to be used in |
66 |
most programs. Perhaps they will eventually be deprecated.) |
most programs. Perhaps they will eventually be deprecated.) |
75 |
<tt>InterruptedExceptions</tt>. |
<tt>InterruptedExceptions</tt>. |
76 |
<li> The <tt>destroy</tt> method, which has never been implemented, |
<li> The <tt>destroy</tt> method, which has never been implemented, |
77 |
has finally been deprecated. This is just a spec change, reflecting |
has finally been deprecated. This is just a spec change, reflecting |
78 |
the fact that that the reason it has never been implmented is that |
the fact that the reason it has never been implemented is that |
79 |
it was undesirable and unworkable. |
it was undesirable and unworkable. |
80 |
</ul> |
</ul> |
81 |
|
|
94 |
|
|
95 |
|
|
96 |
<hr> |
<hr> |
|
<address><A HREF="http://gee.cs.oswego.edu/dl">Doug Lea</A></address> |
|
97 |
</body> |
</body> |
98 |
</html> |
</html> |