Customer Reviews

Linux Socket Programming

5 star:		(1)
4 star:		(3)
3 star:		(1)
2 star:		(1)
1 star:		(2)

 

 

I am really not sure if the other reviewers are leaving comments for the same book. I purchased this book to gain an understanding of socket programming in Linux. I made it half way through chapter 2 before returning the book.
Problems started with chapter 1. The writing style is extremely choppy. The book references sample code on the included CD-ROM and in the back of the book. Guess what? No CD and no code appendix. We are not talking just one reference to this. There are several in chapter one and the part of chapter two I read kept refering to the CD for RFCs.
So, you might say, perhaps there is a web site with code. Eureka! there is. So I happily try to compile the sample simple-client code for chapter 1. One error, one warning, and code that doesn't match what is said in the book. Specifically: the error was caused by forgetting to #include <errno>, warning on line 62 because there needs to be an explicit cast to (struct sockaddr*) and finally in big bold letters in a gray box the author states that the book's sample code will use PF_ prefixes vs AF_. Not true in the code I looked at.
I did email the author and received a quick response. He let me know that he was having to foot the bill for the web site. Shame on the publisher for the lack of support. But shame on Mr. Walton for publishing such unpolished code.
Maybe the rest of the book is ok. Explantions were extremely shallow in chapter one when talking about function calls and structures with references to RFCs and other resources. I paid for the book to be a resource, not to be referred other places. What explanations there were jumped all over the place without any real meat, sometimes using useless analogies. I didn't feel like fighting my way through the rest of it. I broke down and ponied up for Stevens TCP/IP Illustrated Volume 1 and Unix Network Programming Volume 1.

First of all, this book is no UNPv1. If you want to learn network programming for UNIX/Linux, there is nothing that could replace UNPv1 (Stevens "Unix Network Programming" 2nd ed., vol. 1). [CORRECTION: actually Comer's book(s) are comparable to those of Stevens]

Now back to the book reviewed. I bought it because it seemed to elaborate a bit more on a subject covered only briefly by Stevens: concurrent network I/O in real-world conditions. Well, it did have a special section on the subject but it didn't provide any particular information I was looking for:

- analysis of different I/O methods' behavior under different load conditions

- throughput analysis

- applicability of different methods in different UNIX flavours (Oops, this is a book for Linux! Still, it would be nice if the author at least mentioned the portability issues)

- while the examples were nice and clear, it would make sense to create an I/O abstraction layer that would act as a (de)multiplexor and to change only this layer for every I/O paradigm.

So, once we get past the section on real-world network I/O issues, what we are left with is a decent yet not perfect book on network programming. It will teach you how to develop network applications for Linux but it won't provide the same depth UNPv1 does.

Conclusion: Read it if you want to quickly start developing network apps and you don't have time for UNPv1. Otherwise go for UNPv1. Still, it is worthwhile to skim through the sections on throughput and performance.

I think this book is well written, it gives you the basic idea of the network protocal, mainly how each piece is created in a packet. It even goes a little into the Network OSI model, if you dont know about networking, then I can see how this book would seem hard for some ppl. I do admit that i wasnt too happy when i didnt get the cd that the book references too, but if you really need it, you can find it with a little bit of effort, or go to [the website]. Hope this helps those who need it :^).

I bought the book hoping to get some cookbook algorithms for setting up some sockets, but I must say I'm really disappointed with the book. I wish I had read the reviews here first. I would never have purchased the book. I'm an engineer, have been programming for over twenty years and have a large technical book collection. This book is poorly put together, jumps around topics, has confusing explanations, and the incomplete code segments don't help much... I'll think twice about buying another Sam's book. I've read gallies that were better than this. I rate this as a don't buy!

Weel, I was "trying" to find something interesting and finally it happened. The book has a solid explanation of concepts, and every example is quite illustrative. The section that covers Posix threads is very good. And I'm sure that this is the one of the best beginner's guide to socket programming.

If you wants to develop TCP/IP programming, this is THE book.

The main idea of the book is to present a broad overview of the software that uses the Sockets API from a conceptual and practical approach. For several reasons these objectives are not achieved.

The first problem I found is the bad writing style the author uses in order to explain the concepts. From useless methaphors to inconsistent computing jargon, passing by really bad redaction skills; the main text is plagged with non-relevant digressions that could be (if needed at all) put apart in its own chapter. I think 70% of these problems could be eliminated by a good editor review.

About the contents, the book tries to introduce a lot of concepts in an excessive superficial and/or inaccurate way, frequently inserting unimportant details and skipping the basics and really important aspects. For example, in the topic of threads versus processes, the book explains that the Posix Threads is a library and the fork et al. are system calls, etc. and provides a very succinct table of differences and extracts of code showing the API... its not clear from the text nor the samples the fact that the globals are shared between threads, nor the reasons to prefer them over processes or the other way. Next follows a (larger) explanation of the (nonportable and mostly useless) "clone" system call.

Some random additional complains:

- About 20% of the book are appendixes of questionable utility
- In the Kernel API reference, there are Linux-specific system calls (like sched_yield()) mixed with standard ones (like waitpid()) without advice about portability. Ok, this is a "Linux" book, but the author frecuently states the code is mostly usable on Unix.
- Lots of irrelevant pages... templates/persistence/etc on C++, dilemmas on project management(!), etc
- The "SSL/Security" chapter is "filled" with generalities about general security problems (hacking, firewalls, DMZ) but the SSL API is "explained" in sparse comments of a basic two-page code sample! Sadly, this pattern follows for all the "advaced" topics

My advice: like other readers said, do yourself a favor and look for Unix Network Programming Vol 1 of Stevens; or for non serious work just rely on internet tutorials.

I wrote this book mostly for those people that have programmed in C for a number of years and wanted to "step up" to the challenge of network programming. Over the years of programming and socket manipulation, I compiled a cadle-to-grave set of tools, hints, and algorithms that can help anyone who wants to be part of the burgeoning network. I also wrote this for myself -- I wanted to have a central place of notes, something I can put my hands on and use for many years. Yes, this is a technology that is not likely to change, but it will continue to improve. Pick up a copy and see for yourself.
Also, you can get all the programs and some of the notes on my website www.linuxsocket.org. These are free to everyone and are OpenSource. If you have socket algorithms that you would like to share, I will be glad to put them up as well.

I have a MBA degree and program mainly in Delphi Windows Systems. But Delphi now has a Linux functioning operating systems. Back to the book, I do not have a C compiler but I do have a Java compiler which allowed me to run the programs in the Socket Programming book. The program Snooping the NetWork was very enlighting. I am a Project Manager and the information on security was worth the cost of the book. Once I was a Methods Engineer and the book talks about electromagnetic snooping and best of all it gives recommendations on a secure internet system. Sean Walton also has a good handle on the computer industry. He talks about the program flavor of the month and about Design Patterns. Just buy the book. Dean