ACCU Home page ACCU Conference Page
Search Contact us ACCU at Flickr ACCU at GitHib ACCU at Google+ ACCU at Facebook ACCU at Linked-in ACCU at Twitter Skip Navigation

Search in Book Reviews

The ACCU passes on review copies of computer books to its members for them to review. The result is a large, high quality collection of book reviews by programmers, for programmers. Currently there are 1918 reviews in the database and more every month.
Search is a simple string search in either book title or book author. The full text search is a search of the text of the review.
    View all alphabetically
Title:
Java Threads (2nd Edition)
Author:
Scott Oaks&Henry Wong
ISBN:
1 56592 418 5
Publisher:
O'Reilly
Pages:
320pp
Price:
£21-95
Reviewer:
Steve Cornish
Subject:
java
Appeared in:
11-6
This book is an update to the first edition to take advantage of the changes introduced by Java 2. The first four chapters cover the fundamentals of Java Threads that most readers will already be familiar with. These include the Thread and Applet classes, the Runnable interface and the synchronized keyword. However, these chapters are still worth reading as they go into a detail not covered in any Java tutorial book before. As an example, the authors present to the reader which methods have been deprecated on the Thread class, why they were deprecated, and how to achieve the removed functionality properly.

The rest of the book contains information, discussion and examples on common threading issues such as preventing deadlock, preventing lock starvation and thread scheduling. The examples start off trivial, but soon descend into the kind of problems you really could come across.

This is a good book, and certainly, if you're using threads in Java non-trivially then you should have this book. Otherwise, borrow a copy and read the first half to make yourself aware of the threading issues in Java. Even better, think how your code affects others; the section on mixing threads with thread unsafe classes should make you aware of the wider issues surrounding your code, and hopefully, you'll produce well behaved classes that will be easily multi- threaded if the need arises? Do you use the collections? Think hard...