A beginners guide to multi-threading on WIN32. Experienced developers might find it useful to quickly skim through this book to see if there is anything that they didn't already know, but for the most part anyone with significant experience should find a different book.

The language used in the book is very easy to read, making life easy for newcomers to threading, but possibly woolly enough to be slightly dangerous too, in that some stuff could bits could be misinterpreted. Developing example code using incorrect practices and then slowly fixing the problems is informative, but possibly not the best way of doing things. Why not just go for the right way first and then point out the errors that could have been made? That way it is safe for people to dip into the book and use code as is, rather than having to trawl through for a correct version. Talking about using code from books - do the authors expect the reader to trust their code when they include comments like "This happens occasionally instead of end-of-file. Not sure why" ? Certainly, that means that I would code-review anything I lifted from this book very carefully. More likely, it means that I won't lift anything from this book and will use Jeffrey Richter or Richard Gerber/Andrew Binstock instead.

The book does cover a large range of Windows-related multi-threading topics - from file handling, GUI handling etc through implications for DLLs. It touches on Sockets but only very briefly, which was disappointing. Also particularly disappointing were the chapters on debugging and inter-process communications. There are too many books around that say that testing/debugging multi-threaded code is difficult without coming up with good strategies for overcoming the difficulties. Unit testing, logging and the debugger are useful, but obvious. "you must start making predictions (otherwise known as guesses)" (p268) is certainly an approach, but perhaps the time has come to use an engineering approach?

The material could do with updating, as Windows, C++ and development techniques have all moved on since this book was published. Experienced developers should look forward to Jeffrey Richter's new book, planned for end of 2007, which should be as up to date as it comes.

Despite referring to the CD-ROM the book didn't actually come with one. Instead the source had to be downloaded from the Addison Wesley web-site. Strangely, Addison Wesley do not have an errata for this book on their web-site. Normally I'm a big Addison Wesley fan, but they have done a few silly things with this book. The very first page of the preface had me concerned, when they hyphenated _beginthread to be _begin-thread. Given that this book is aimed at beginners I would be pretty sure that someone, somewhere tried typing that into their computer complete with the hyphen.

It does a very good job at describing the Win32 API for multithreading but the applications of multithreading assumed is strictly I/O related (Networking,printing,writing/reading files). The set of techniques for parallel processing on the same data is completely absent such as data organization in memory to optimize its parallel access. This is probably due to the age of the book as when it has been written, single core processor system was the norm. Parallel processing will become very important with the growing popularity of the multi core systems. Despite this weakness, this book is still my best recommendation for learning multithreaded programming on Windows since, to my knowledge, there is not yet any book tackling the subject of parallel processing on a Windows/x86 platform.

Quite useful book. But I wont recommend it. Other than file I/O and threading, it is not for advanced programmers.

From the beginning to end, it only imparts about Win95 and WinNT. None of the OS after Windows 98 are covered. So, much of information covered is obsolete.

I was looking to a complete multithreading book for Windows XP, COM threading models, writing perfect multithreaded GUI application.

This material is still relevent, even when using .NET. The discussion of Win32 multithreading transcends any particular development environment used with a Windows 32 bit environment.

The key idea behind this book is getting correct, reproducible results with windows multithreaded applications. Multithreaded applications are very hard to get right and even harder to properly test. The author explains the many sources of problems and how to avoid them.

In order to understand this book's code samples, you will have to understand the Win32 API and code written in Visual C++ for Windows NT. It is important to see examples of these concepts in code.

I bought this book to get advanced concepts of win32 multithreading which I cant get by browsing through msdn. Although this book has covered all topics, I was expecting more like a "Concurrent Programming In Java, by Doug Lee" kind of book which has a lot of gotchas. I would recommend this book for beginners looking for examples of how to use the APIs. Advanced developers should look somewhere else.

If you are looking to know in depth about multithreading in windows
with differences in unix, very good examples and useful information, please, check out this book.