UNIX Systems Programming: Communication - Concurrency and Threads
In a nutshell, this updated UNIX classic covers everything you'll ever need for threads, TCP/IP and RPC programming--with reusable code examples that explain syntax along the way. Robbins and Robbins explain the essentials of UNIX programming, concentrating on communication, concurrency, and multithreading techniques and why, when, and how to use them. They also show how to design complex software to get the best from the UNIX operating system. Using short code snippets to illustrate how to use system calls, they also include a number of hands-on "projects" that very quickly help readers expand their skill levels. The book includes chapters on files, signals, semaphores, POSIX threads, client-server communication, and remote procedure calls. There are also short examples, working code, and simplified libraries for use in network communication applications featured throughout the book. The updated Second Edition includes all-new chapters on the Web and multicast and a completely revised and updated RPC chapter.
User Reviews about UNIX Systems Programming: Communication - Concurrency and Threads
This is an awesome book. You'll have to be patient when going through it. And you'll learn a lot if you follow along with the examples and make everything work. It took me probably 6 hours just to get through chapter 2 - not because I can't read, but because I'm paying attention to every little detail, and making sure I learn what's going on.
The other thing that came as a big surprise, was that this is the best introduction to C i've come across. I've read quite a few books on C. Generally, I get through these other books on C - I get the syntax and pointers, and headers, etc. What I can never get through in these other C books, is that they use Math for all the examples. Which bores me, and sometimes frustrates me - because what I want to do with systems programming is not math - that's just me.
Of all the C books I've read, this one, and "C - A Reference Manual 5th Edition" are the best C books.
One pitfall in the book, is that with most of the examples, the conditionals to check pointers, and some other conditionals are somewhat amateur looking (that's just me). For example, in chapter 2, the "listlib.c" file has tons of conditionals like this:
list_t **newptrs;
if(headptr == NULL)
{
errno = EINVAL;
return -1;
}
That started to confuse me, why not just write:
list_t **newptrs;
if(!headptr)
{
errno = EINVAL;
return -1;
}
Which is ok. So there are many times where it seems the author is either purposefully writing conditionals to be verbose for readers, or doesn't know how to simplify with "not" flips.
Another example:
if(ptr != NULL)
can be simplified to:
if(ptr)
Other than those small things, this book is great. -- It's a lot more than just concurrency - it's the best introduction to C i've seen.
This is an invaluable reference to keep close at hand if you are a programmer supporting UNIX. The only thing I didn't find in this text is how to change your process name on-the-fly. Everything else I've looked for was there, and in most cases, described in detail.
If you do systems programming on UNIX then you should have this book. -- Relatively thorough reference.
This book contains the answers to almost any question concerning communication, concurrency and threads. All of the included code works fine, but is often ugly. At least the ugly code is available online if you are too lazy to write your own, or type it yourself.
3 stars because this book follows the typical computer book pattern. It's too big. Huge examples and discussion for rarely used features, when a table enumerating specifics would be better. There is alot of fluff, but at least the material is there. -- Comprehensive
I read it in one of the book store in three hours. I bought it a month later. It saved me several times. One of the best books I have ever had. -- Worth my yearly salary!
This is the type of book that doesn't leave you with more questions than it answers. It doesn't just discuss the concepts and then you're on your own for coding. It gives you enough code and explanation so that you can implement mutex locks, semaphores, threads, etc. It doesn't force you to go search online for code samples. I refer to this book often, and not just when writing code for Unix. -- practical it is
Top Search
Last Search
