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