| 1 |
|
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
| 2 |
|
<html> |
| 3 |
|
<head> |
| 4 |
< |
<title>JSR 166 Community Review Draft Introduction.</title> |
| 4 |
> |
<title>JSR 166 Introduction.</title> |
| 5 |
|
</head> |
| 6 |
|
|
| 7 |
|
<body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000"> |
| 8 |
< |
<h1>JSR 166 Community Review Draft Introduction.</h1> |
| 8 |
> |
<h1>JSR 166 Introduction.</h1> |
| 9 |
|
|
| 10 |
|
by <a href="http://gee.cs.oswego.edu/dl">Doug Lea</a> |
| 11 |
|
<p> |
| 12 |
|
|
| 13 |
< |
To chack for updates to this draft, access a preliminary prototype |
| 14 |
< |
release of main functionality, or join a mailing list discussing this |
| 15 |
< |
JSR, go to: <A |
| 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 |
| 17 |
|
HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> |
| 18 |
|
http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A> |
| 19 |
< |
. |
| 19 |
< |
<p> |
| 19 |
> |
. <p> |
| 20 |
|
|
| 21 |
|
<em> <b>Disclaimer</b>. The prototype implementation is experimental |
| 22 |
|
code developed as part of JCP JSR-166 is made available to the |
| 68 |
|
|
| 69 |
|
<h2>Threads</h2> |
| 70 |
|
|
| 71 |
< |
Two minor changes are introduced to the {@link java.lang.Thread} |
| 72 |
< |
class: It now allows per-thread installation of handlers for uncaught |
| 73 |
< |
exceptions. Ths optionally disassociates handlers from ThreadGroups, |
| 74 |
< |
which has proven to be too inflexible. (Note that the combination of |
| 75 |
< |
features in JSR-166 make ThreadGroups even less likely to be used in |
| 76 |
< |
most programs. Perhaps they will eventually be deprecated.) Secondly, |
| 77 |
< |
access checks are no longer required when a Thread interrupts |
| 78 |
< |
<em>itself</em>. The <tt>interrupt</tt> method is the only way to |
| 79 |
< |
re-assert a thread's interruption status (and in the case of |
| 80 |
< |
self-interruption has no other effect than this). The check here |
| 81 |
< |
previously caused unjustifiable and uncontrollable failures when |
| 82 |
< |
restricted code invoked library code that must reassert interruption |
| 83 |
< |
to correctly propagate status when encountering some |
| 84 |
< |
<tt>InterruptedExceptions</tt>. |
| 71 |
> |
Three minor changes are introduced to the {@link java.lang.Thread} |
| 72 |
> |
class: |
| 73 |
> |
<ul> |
| 74 |
> |
<li> It now allows per-thread installation of handlers for uncaught |
| 75 |
> |
exceptions. Ths optionally disassociates handlers from ThreadGroups, |
| 76 |
> |
which has proven to be too inflexible. (Note that the combination of |
| 77 |
> |
features in JSR-166 make ThreadGroups even less likely to be used in |
| 78 |
> |
most programs. Perhaps they will eventually be deprecated.) |
| 79 |
> |
|
| 80 |
> |
<li> Access checks are no longer required when a Thread interrupts |
| 81 |
> |
<em>itself</em>. The <tt>interrupt</tt> method is the only way to |
| 82 |
> |
re-assert a thread's interruption status (and in the case of |
| 83 |
> |
self-interruption has no other effect than this). The check here |
| 84 |
> |
previously caused unjustifiable and uncontrollable failures when |
| 85 |
> |
restricted code invoked library code that must reassert interruption |
| 86 |
> |
to correctly propagate status when encountering some |
| 87 |
> |
<tt>InterruptedExceptions</tt>. |
| 88 |
> |
<li> The <tt>destroy</tt> method, which has never been implemented, |
| 89 |
> |
has finally been deprecated. This is just a spec change, reflecting |
| 90 |
> |
the fact that that the reason it has never been implmented is that |
| 91 |
> |
it was undesirable and unworkable. |
| 92 |
> |
</ul> |
| 93 |
|
|
| 94 |
|
<h2>Timing</h2> |
| 95 |
|
|
