--- jsr166/src/main/intro.html 2003/09/27 12:21:56 1.14 +++ jsr166/src/main/intro.html 2004/11/21 01:40:32 1.19 @@ -10,22 +10,23 @@ by Doug Lea

-This is an updated version of the specification submitted for JCP Public -Review. To check for further updates, access a preliminary prototype -release of main functionality, or join a mailing list discussing -JSR-166, go to: http://altair.cs.oswego.edu/mailman/listinfo/concurrency-interest. -

Note: The javadocs here includes some existing java.util -Collection interfaces and classes that are not part of the JSR-166 -spec, but are included because JSR-166 methods implement or inherit -from their specifications. +

Note: The javadocs here do not include pre-existing +java classes (for example java.lang.Thread) that were changed +as part of the JSR166 spec. On the other hand, the javadocs here so +include some existing java.util Collection interfaces and classes that +are not part of the spec, but are included because some new methods +implement or inherit from their specifications. +

JSR-166 introduces package java.util.concurrent containing utility classes commonly useful in concurrent programming. Like package java.util, it includes a few small -standardized extensible frameworks, as well as some classes that +standardized extensible frameworks, as well as other classes that provide useful functionality and are otherwise tedious or difficult to implement. @@ -37,8 +38,8 @@ pools. This diversity reflects the range of contexts in which developers of concurrent programs have been found to require or desire support not previously available in J2SE, which also keeping the -resulting package small; providing only functionality that it makes -sense to standardize. +resulting package small; providing only functionality that has been +found to be worthwhile to standardize.

Descriptions and brief motivations for the main components may be found in the associated package documentation. JSR-166 also includes @@ -74,7 +75,7 @@ InterruptedExceptions.

  • The destroy method, which has never been implemented, has finally been deprecated. This is just a spec change, reflecting - the fact that that the reason it has never been implmented is that + the fact that that the reason it has never been implemented is that it was undesirable and unworkable.