Originally posted by Ko Ko Naing:
Hi Henry,
I just would like to know whether the book needs to be read one chapter by one? Or are the topics discussed in chapter-independent way like we can open up the book, choose any chapter we want and we can easily get the idea from that chapter without reading the previous chapters?
Thanks a lot...
It depends... the first four chapters should be read prior to any other chapter. It is very hard to understand the later chapters without the basics. The other chapters are pretty independent of each other, but still, there are a few dependencies.
The I/O chapter depends on the threadpool chapter, but quite frankly, readers should be more concerned with its dependency on NIO -- which requires a whole other book...
The task scheduling chapter also needs the
thread pool chapter.
The performance chapter depends on the whole book, as it is running performance tests for issues that were raised throughout the book.
The rest of the chapters should be fine to be read independently... One more issue. Scott and I spent a lot of time worrying about the ordering of the chapters. The natural order may actually be the best way to read it...
Henry