ViewVC logotype

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

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

revision 1.1 by tim, Fri May 16 14:13:04 2003 UTC revision 1.14 by dl, Sat Sep 27 12:21:56 2003 UTC
# Line 1  Line 1 
2  <html>  <html>
3   <head>   <head>
4     <title>JSR 166 Snapshot Introduction.</title>     <title>JSR 166 Introduction.</title>
5    </head>    </head>
7    <body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000">    <body bgcolor="#ffffee" vlink="#0000aa" link="#cc0000">
8    <h1>JSR 166 Snapshot Introduction.</h1>    <h1>JSR 166 Introduction.</h1>
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>
13  To join a mailing list discussing this JSR, go to:  This is an updated version of the specification submitted for JCP Public
14  <A HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest"> http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A> .  Review.  To check for further updates, access a preliminary prototype
15    release of main functionality, or join a mailing list discussing
16  <p>  JSR-166, go to: <A
17  <em>  HREF="http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest">
18   Disclaimer - This prototype is experimental code developed as part of  http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest</A>.
19   JSR166 and made available to the developer community for use  
20   as-is. It is not a supported product. Use it at your own risk. The  <p><em>Note: The javadocs here includes some existing java.util
21   specification, language and implementation are subject to change as a  Collection interfaces and classes that are not part of the JSR-166
22   result of your feedback. Because these features have not yet been  spec, but are included because JSR-166 methods implement or inherit
23   approved for addition to the Java language, there is no schedule for  from their specifications.</em>
24   their inclusion in a product.  
25  </em>  <p> JSR-166 introduces package <tt>java.util.concurrent</tt>
26    containing utility classes commonly useful in concurrent
27  <p>  programming. Like package <tt>java.util</tt>, it includes a few small
28  Package java.util.concurrent contains utility classes that are  standardized extensible frameworks, as well as some classes that
29  commonly useful in concurrent programming. Like package java.util, it  provide useful functionality and are otherwise tedious or difficult to
30  includes a few small standardized extensible frameworks, as well as  implement.
31  some classes that provide useful functionality and are otherwise  
32  tedious or difficult to implement.  In this JSR, we have been  <p>JSR-166 focusses on breadth, providing critical functionality
33  conservative in selecting only those APIs and implementations that are  useful across a wide range of concurrent programming styles and
34  useful enough to encourage nearly all concurrent programmers to use  applications, ranging from low-level atomic operations, to
35  routinely.  JSR 166 also includes a few changes and additions in  customizable locks and synchronization aids, to various concurrent
36  packages outside of java.util.concurrent: java.lang, to address  data structures, to high-level execution agents including thread
37  uncaught exceptions, and java.util to better integrate queues.  pools. This diversity reflects the range of contexts in which
38  The API covers:  developers of concurrent programs have been found to require or desire
39    support not previously available in J2SE, which also keeping the
40    <ul>  resulting package small; providing only functionality that it makes
41      <li> Queues  sense to standardize.
42      <li> Executors  
43      <li> Locks  <p>Descriptions and brief motivations for the main components may be
44      <li> Condition variables  found in the associated package documentation.  JSR-166 also includes
45      <li> Atomic variables  a few changes and additions in packages outside of
46      <li> Timing  java.util.concurrent.  Here are brief descriptions.
     <li> Synchronizers  
     <li> Concurrent Collections  
     <li> Uncaught Exception Handlers  
 The main rationale for JSR 166 is that threading primitives, such as  
 synchronized blocks, Object.wait and Object.notify, are insufficient  
 for many programming tasks.  Currently, developers can use only the  
 concurrency control constructs provided in the Java language  
 itself. These are too low level for some applications, and are  
 incomplete for others.  As a result, application programmers are often  
 forced to implement their own concurrency facilities, resulting in  
 enormous duplication of effort creating facilities that are  
 notoriously hard to get right and even harder to optimize.  Offering a  
 standard set of concurrency utilities will ease the task of writing a  
 wide variety of multithreaded applications and generally improve the  
 quality of the applications that use them.  
 Here are brief descriptions and rationales of the main components.  
 For details see the javadocs at <a  
48  <h2>Queues</h2>  <h2>Queues</h2>
50  A basic (nonblocking) Queue interface that is compatatible with  A basic (nonblocking) {@link java.util.Queue} interface extending
51  java.util.Collections will be introduced into java.util. Also,  {@link java.util.Collection} is introduced into
52  although it is at the borders of being in scope of JSR-166,  <tt>java.util</tt>. Existing class {@link java.util.LinkedList} is
53  java.util.LinkedList will be adapted to support Queue, and  adapted to support Queue, and a new non-thread-safe {@link
54  a new non-thread-safe java.util.HeapPriorityQueue will be added.  java.util.PriorityQueue} is added.
56  <p> Five implementations in java.util.concurrent support the extended  <h2>Threads</h2>
57  BlockingQueue interface, that defines blocking versions of put and  
58  take: LinkedBlockingQueue, ArrayBlockingQueue, SynchronousQueue,  Three minor changes are introduced to the {@link java.lang.Thread}
59  PriorityBlockingQueue, and DelayQueue. Additionally,  class:
60  java.util.concurrent.LinkedQueue supplies an efficient thread-safe  <ul>
61  non-blocking queue.    <li> It now allows per-thread installation of handlers for uncaught
62      exceptions. Ths optionally disassociates handlers from ThreadGroups,
63  <p> Since the target release is JDK1.5, and generics are slated to be    which has proven to be too inflexible. (Note that the combination of
64  in 1.5, Queues are parametrized on element type. (Also some others    features in JSR-166 make ThreadGroups even less likely to be used in
65  below.)    most programs. Perhaps they will eventually be deprecated.)
67      <li> Access checks are no longer required when a Thread interrupts
68  <h2>Executors</h2>    <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  Executors provide a simple standardized interface for defining custom    self-interruption has no other effect than this).  The check here
71  thread-like subsystems, including thread pools, asynch-IO, and    previously caused unjustifiable and uncontrollable failures when
72  lightweight task frameworks.  Executors also standardize ways of    restricted code invoked library code that must reassert interruption
73  calling threads that compute functions returning results, via    to correctly propagate status when encountering some
74  Futures. This is supported in part by defining interface Callable, the    <tt>InterruptedExceptions</tt>.
75  argument/result analog of Runnable.    <li> The <tt>destroy</tt> method, which has never been implemented,
76      has finally been deprecated. This is just a spec change, reflecting
77  <p> While the Executor framework is intended to be extensible the most    the fact that that the reason it has never been implmented is that
78  commonly used Executor will be ThreadExecutor, which can be configured    it was undesirable and unworkable.
79  to act as all sorts of thread pools, background threads, etc. The  </ul>
 class is designed to be general enough to suffice for the vast  
 majority of usages, even sophisticated ones, yet also includes methods  
 and functionality that simplify routine usage.  
 The Lock interface supports locking disciplines that differ in  
 semantics (reentrant, semaphore-based, etc), and that can be used in  
 non-block-structured contexts including hand-over-hand and lock  
 reordering algorithms. This flexibility comes at the price of more  
 awkward syntax.  Implementations include Semaphore, ReentrantMutex  
 FIFOSemaphore, and CountDownLatch.  
 The Locks class additionally supports trylock-designs using builtin  
 locks without needing to use Lock classes.  This requires adding new  
 capabilities to builtin locks inside JVMs.  
 A ReadWriteLock interface similarly defines locks that may be shared  
 among readers but are exclusive to writers. For this release, only a  
 single implementation, ReentrantReadWriteLock, is planned, since it  
 covers all standard usage contexts. But programmers may create their  
 own implementations to cover nonstandard requirements.  
 A Condition class provides the kinds of condition variables associated  
 with monitors in other cocurrent languages, as well as pthreads  
 condvars.  Their support reduces the need for tricky and/or  
 inefficient solutions to many classic concurrent problems.  Conditions  
 also address the annoying problem that Object.wait(msecs) does not  
 return an indication of whether the wait timed out. This leads to  
 error-prone code. Since this method is in class Object, the problem is  
 basically unfixable.  
 To avoid compatibility problems, the names of Condition methods need  
 to be different than Object versions. The downside of this is that  
 people can make the mistake of calling cond.notify instead of  
 cond.signal. However, they will get IllegalMonitorState exceptions if  
 they do, so they can detect the error if they ever run the code.  
 The implementation requires VM magic to atomically suspend and release  
 lock. But it is unlikely to be very challenging for JVM providers,  
 since most layer Java monitors on top of posix condvars or similar  
 low-level functionality anyway.  
 <h2>Atomic variables</h2>  
 Classes AtomicInteger, AtomicLong, AtomicDouble, AtomicFloat, and  
 AtomicReference provide simple scalar variables supporting  
 compareAndSwap (CAS) and related atomic operations. These are  
 desparately needed by those performing low-level concurrent system  
 programming, but much less commonly useful in higher-level frameworks.  
81  <h2>Timing</h2>  <h2>Timing</h2>
83  Java has always supported sub-millisecond versions of several native  Method <tt>nanoTime</tt> is added to {@link java.lang.System}. It
84  time-out-based methods (such as Object.wait), but not methods to  provides a high-precision timing facility that is distinct from and
85  actually perform timing in finer-grained units. We address this by  uncoordinated with <tt>System.currentTimeMillis</tt>.
86  introducing class Clock, which provides multiple granularities for  
87  both accessing time and performing time-out based operations.  <h2>Removing ThreadLocals</h2>
89    The {@link java.lang.ThreadLocal} class now supports a means to remove
90  <h2>Synchronizers</h2>  a ThreadLocal, which is needed in some thread-pool and worker-thread
91    designs.
92  Five classes aid common special-purpose synchronization idioms.  
93  Semaphores and FifoSemaphores are classic concurrency tools.  Latches  
 are very simple yet very common objects useful for blocking until a  
 single signal, event, or condition holds.  CyclicBarriers are  
 resettable multiway synchronization points very common in some styles  
 of parallel programming. Exchangers allow two threads to exchange  
 objects at a rendezvous point.  
 <h2>Concurrent Collections</h2>  
 JSR 166 will supply a few Collection implementations designed for use  
 in multithreaded contexts: ConcurrentHashTable, CopyOnWriteArrayList,  
 and CopyOnWriteArraySet.  
 <h2>Uncaught Exception Handlers</h2>  
 The java.lang.Thread class will be modified to allow per-thread  
 installation of handlers for uncaught exceptions. Ths optionally  
 disassociates these handlers from ThreadGroups, which has proven to be  
 too inflexible in many multithreaded programs. (Note that the combination  
 of features in JSR 166 make ThreadGroups even less likely to  
 be used in most programs. Perhaps they will eventually be deprecated.)  
 Additionally,  ThreadLocals will now support a means to  
 remove a ThreadLocals, which is needed in some thread-pool and  
 worker-thread designs.  
95    <hr>    <hr>
   <address><A HREF="http://gee.cs.oswego.edu/dl">Doug Lea</A></address>  
96   </body>   </body>
97  </html>  </html>

Removed from v.1.1  
changed lines
  Added in v.1.14

ViewVC Help
Powered by ViewVC 1.1.27