[cvs] / jsr166 / src / main / intro.html Repository:
ViewVC logotype

Diff of /jsr166/src/main/intro.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.11, Wed Aug 6 17:40:20 2003 UTC revision 1.23, Thu Jul 23 16:57:39 2015 UTC
# Line 1  Line 1 
1  <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">  <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
2  <html>  <html>
3   <head>   <head>
4     <title>JSR 166 Community Review Draft Introduction.</title>     <title>JSR 166 Introduction.</title>
5    </head>    </head>
6    
7    <body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000">    <body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000">
8    <h1>JSR 166 Community Review Draft Introduction.</h1>    <h1>JSR 166 Introduction.</h1>
9    
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  To check for updates to this draft, access a preliminary prototype  This is maintenance repository of JSR166 specifications.  For further
14  release of main functionality, or join a mailing list discussing this  information, go to: <A
 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
# Line 50  Line 38 
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
# Line 68  Line 56 
56    
57  <h2>Threads</h2>  <h2>Threads</h2>
58    
59  Two minor changes are introduced to the {@link java.lang.Thread}  Three minor changes are introduced to the {@link java.lang.Thread}
60  class: It now allows per-thread installation of handlers for uncaught  class:
61  exceptions. Ths optionally disassociates handlers from ThreadGroups,  <ul>
62      <li> It now allows per-thread installation of handlers for uncaught
63      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.) Secondly,    most programs. Perhaps they will eventually be deprecated.)
67  access checks are no longer required when a Thread interrupts  
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  <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  re-assert a thread's interruption status (and in the case of
71  self-interruption has no other effect than this).  The check here  self-interruption has no other effect than this).  The check here
# Line 82  Line 73 
73  restricted code invoked library code that must reassert interruption  restricted code invoked library code that must reassert interruption
74  to correctly propagate status when encountering some  to correctly propagate status when encountering some
75  <tt>InterruptedExceptions</tt>.  <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 the reason it has never been implemented is that
79      it was undesirable and unworkable.
80    </ul>
81    
82  <h2>Timing</h2>  <h2>Timing</h2>
83    
# Line 98  Line 94 
94    
95    
96    <hr>    <hr>
   <address><A HREF="http://gee.cs.oswego.edu/dl">Doug Lea</A></address>  
97   </body>   </body>
98  </html>  </html>

Legend:
Removed from v.1.11  
changed lines
  Added in v.1.23

Doug Lea
ViewVC Help
Powered by ViewVC 1.0.8