Talk:Java concurrency package: Difference between revisions
imported>Pat Palmer (→History and opinion: Executor question) |
imported>Pat Palmer (→Executors section: elaboration of my earlier comment) |
||
| Line 17: | Line 17: | ||
===Executors section=== | ===Executors section=== | ||
It would be helpful to explain why using an Executor (2 lines of code) is preferred over explicitly launching one thread (1 line of code).[[User:Pat Palmer|Pat Palmer]] 02:19, 17 August 2010 (UTC) | It would be helpful to explain why using an Executor (2 lines of code) is preferred over explicitly launching one thread (1 line of code). The section ends by speaking of "low-level details of thread management"; this needs to have some examples cited, because as it stands, it is not clear to me why I might want to use an Executor rather than creating a thread explicitly.[[User:Pat Palmer|Pat Palmer]] 02:19, 17 August 2010 (UTC) | ||
Revision as of 20:20, 16 August 2010
overall comments
This is a great beginning. The article as it stands today is already useful. Some suggested enhancements which might still be done are detailed in the following subsections:Pat Palmer 01:43, 17 August 2010 (UTC)
what features are in Java 5.0 vs. Java 6.0
My understanding is that Java 6.0 introduced some new data synchronization constructs into the language. This article would benefit from stating clearly what came with Java 5.0, and then what was added in Java 6.0. The release date for Java 5.0 does occur later in the article, and this should (IMO) be moved to the article introduction to provide a context for this article.Pat Palmer 01:43, 17 August 2010 (UTC)
- Specifically, someone could compare this Java 5 summary: http://download.oracle.com/javase/1.5.0/docs/api/java/util/concurrent/package-summary.html with this Java 6 summary: http://download-llnw.oracle.com/javase/6/docs/api/java/util/concurrent/package-summary.html and list out the new capabilities within each of the five areas identified on the Java API page.
Definitions all done by quotes
Directly quoting another author for every definition of a term seems like overkill. Definitions should generally be paraphrased into one's own words. The only reason for placing a reference on the definition of a widely-known term is if the person or source being cited is being given credit for inventing the concept represented by the term. These "definition quotes" all need to be transformed. The references can be kept by placing a pointer to the reference on the Bibiography or External Links tabs.Pat Palmer 01:50, 17 August 2010 (UTC)
History and opinion
The first paragraph of the history section starts with a statement about what was "historically" the case. People do not always agree on matters such as this, so it's probably important (in addition to providing the reference where the statement came from), to add to the text words such as "according to Deitel et al." or some such.Pat Palmer 02:00, 17 August 2010 (UTC)
Executors section
It would be helpful to explain why using an Executor (2 lines of code) is preferred over explicitly launching one thread (1 line of code). The section ends by speaking of "low-level details of thread management"; this needs to have some examples cited, because as it stands, it is not clear to me why I might want to use an Executor rather than creating a thread explicitly.Pat Palmer 02:19, 17 August 2010 (UTC)