ViewVC Help
View File | Revision Log | Show Annotations | Download File | Root Listing
root/jsr166/jsr166/src/main/intro.html
(Generate patch)

Comparing jsr166/src/main/intro.html (file contents):
Revision 1.11 by tim, Wed Aug 6 17:40:20 2003 UTC vs.
Revision 1.14 by dl, Sat Sep 27 12:21:56 2003 UTC

# Line 1 | Line 1
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 check 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 Public
14 > Review.  To check for further updates, access a preliminary prototype
15 > release of main functionality, or join a mailing list discussing
16 > JSR-166, 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 < .
20 < <p>
21 <
22 < <em> <b>Disclaimer</b>. The prototype implementation is experimental
23 < code developed as part of JCP JSR-166 is made available to the
23 < developer community for use as-is. It is not a supported product. Use
24 < it at your own risk. The specification, language and implementation
25 < are subject to change as a result of your feedback. Because these
26 < features have not yet been approved for addition to the Java language,
27 < 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 > http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A>.
19 >
20 > <p><em>Note: The javadocs here includes some existing java.util
21 > Collection interfaces and classes that are not part of the JSR-166
22 > spec, but are included because JSR-166 methods implement or inherit
23 > from their specifications.</em>
24  
25   <p> JSR-166 introduces package <tt>java.util.concurrent</tt>
26   containing utility classes commonly useful in concurrent
# Line 50 | Line 37 | data structures, to high-level execution
37   pools. This diversity reflects the range of contexts in which
38   developers of concurrent programs have been found to require or desire
39   support not previously available in J2SE, which also keeping the
40 < resulting package small; providing only that minimial support for
41 < which it makes sense to standardize.
40 > resulting package small; providing only functionality that it makes
41 > sense to standardize.
42  
43   <p>Descriptions and brief motivations for the main components may be
44   found in the associated package documentation.  JSR-166 also includes
# Line 68 | Line 55 | java.util.PriorityQueue} is added.
55  
56   <h2>Threads</h2>
57  
58 < Two minor changes are introduced to the {@link java.lang.Thread}
59 < class: It now allows per-thread installation of handlers for uncaught
60 < exceptions. Ths optionally disassociates handlers from ThreadGroups,
61 < which has proven to be too inflexible. (Note that the combination of
62 < features in JSR-166 make ThreadGroups even less likely to be used in
63 < most programs. Perhaps they will eventually be deprecated.) Secondly,
64 < access checks are no longer required when a Thread interrupts
65 < <em>itself</em>.  The <tt>interrupt</tt> method is the only way to
66 < re-assert a thread's interruption status (and in the case of
67 < self-interruption has no other effect than this).  The check here
68 < previously caused unjustifiable and uncontrollable failures when
69 < restricted code invoked library code that must reassert interruption
70 < to correctly propagate status when encountering some
71 < <tt>InterruptedExceptions</tt>.
58 > Three minor changes are introduced to the {@link java.lang.Thread}
59 > class:
60 > <ul>
61 >  <li> It now allows per-thread installation of handlers for uncaught
62 >  exceptions. Ths optionally disassociates handlers from ThreadGroups,
63 >  which has proven to be too inflexible. (Note that the combination of
64 >  features in JSR-166 make ThreadGroups even less likely to be used in
65 >  most programs. Perhaps they will eventually be deprecated.)
66 >
67 >  <li> Access checks are no longer required when a Thread interrupts
68 >  <em>itself</em>.  The <tt>interrupt</tt> method is the only way to
69 >  re-assert a thread's interruption status (and in the case of
70 >  self-interruption has no other effect than this).  The check here
71 >  previously caused unjustifiable and uncontrollable failures when
72 >  restricted code invoked library code that must reassert interruption
73 >  to correctly propagate status when encountering some
74 >  <tt>InterruptedExceptions</tt>.
75 >  <li> The <tt>destroy</tt> method, which has never been implemented,
76 >  has finally been deprecated. This is just a spec change, reflecting
77 >  the fact that that the reason it has never been implmented is that
78 >  it was undesirable and unworkable.
79 > </ul>
80  
81   <h2>Timing</h2>
82  
# Line 98 | Line 93 | designs.
93  
94  
95    <hr>
101  <address><A HREF="http://gee.cs.oswego.edu/dl">Doug Lea</A></address>
96   </body>
97   </html>

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines