unix

Great book, I've read it cover to cover. But why buy it when the author has newer versions out? Because (1) it is more concise and (2) it has info not in the other editions. I recommend you read this one cover-to-cover and buy the others as more detailed reference. His 3 other books (Advanced Programming in the Unix Environment, Unix Net. Prog.,2nd Ed., Vol.1; Unix Net. Programming, 2nd Ed., Vol.2) are far more detailed and worth having, but each is very thick. AND, the author died without finishing Unix Network Programming, 2nd Ed., Vol.3 (Applications). You have to buy this older edition to get the applications. It's easier to read 1 book 700 pp. long than to read 3 books, each 700 pp. long. Time is money.

Network programming was never meant to be easy. It has simply too many details and functions, to make it mind boggling. So an excellent reference is in order.

I had read TCP/IP Illustrated I by Richard Stevens and found it an excellent read. Which is why I bought this book. Frankly, I was a bit dissapointed with it.

In the TCP/IP book, Stevens explains concepts with the help of diagrams and examples. This book, on the other hand, reads like a listing of various programs which make no sense. I found it very diffcult to use as my first programming book.

If you have some knowledge of network programming, you shuld buy this book. But if you are a novice like me, then think twice about it.

I have been actively involved in computer software/hardware for close to 20 years and have purchased probably 200+ books in this time period. Over 75% I wish I hadn't purchased. This book is probably in my top 10 however.

This book is what's called a "Bible". It's an authoritive reference on Unix networking and communications (ipc/rpc) and much else. I equate it to the Kernighan & Ritchie C book, etc.

I wouldn't recommend this book to someone new to computers, but if you have a few years under your belt, or are an eager-beaver then go ahead...you won't regret your purchase.

The author uses a simple client/server program example (a simple file server) and then goes through several iterations/revisions, each using a different IPC mechanism to accomplish same task. A great technique for exploring new concepts...tie them all to a single program design with the program evolving to use different APIs/IPC mechanisms.