Linux Socket Programming presents a comprehensive discussion of all relevant topics including: writing programs compatible with both Internet Protocol version 4 (IPv4) and IPv6, raw sockets, User Datagram Protocol (UDP), broadcasting /multicasting, server internals, and more, plus a section covering Posix threads.It provides thorough coverage of programming with the TCP, UDP, and IP protocols, as well as lower-level raw sockets. The myriad of function calls, data structures, and options associated with the APIs are explained with well-chosen diagrams and tables.
--This text refers to an alternate
Paperback
edition.
| |||||||||||||||
Book Description
Editorial Reviews
About the Author
Sean Walton MSCS, formerly a lead design technology specialist and configuration management team lead on the process improvement team at Nationwide Financial has also worked for Hewlett Packard where he developed the automatic language detection feature found on the LaserJet printers (patent #5,392,419). Sean also developed a real time micro operating system for the 8052 microcontroller for emulating printer engines. Sean got his MSCS in 1990 from BYU specializing in merging language and multitasking theory. He has many years of professional experience in several types of UNIX programming and administration including Linux, Ultrix, SunOS and System V. Because of this background, he focuses on system-independent programming that facilitates easy porting.
--This text refers to an alternate
Paperback
edition.
Product Details
Would you like to update product info or give feedback on images?
|
More About the Author
I have always loved fiction, the more fantastic the better. When I was eleven I got a paper route with the Hartford Courant, but early morning delivery was tediously boring. So, I told myself stories to keep myself occupied. Now, learning that I talked to myself may seem a little odd to you, but who's to say that all of us are not a little cracked in some way?
When I was a teenager, I discovered computers (this was before the IBM PC days!), and I knew that would be career. I went to Brigham Young University and, later, University of Utah where I completed a Bachelors of Science, a Masters of Science, and a Masters of Philosophy in Computer Science. The intervening time was spent working for Hewlett Packard, Nationwide, American Electric Power, etc.
In 2001, SAMS Publishing gave me the privilege of writing a book for them called Linux Socket Programming. They were amazing, and I would write for them again in a heartbeat. It may sound strange, but I wrote this book for myself -- I wanted to create for myself a reference, but I knew that simplifying network programming would become essential for all network programmers. Another book written by Stevens was too academic for the typical programmer who was trying to meet a deadline. But, technical writing wasn't enough.
I have a beautiful wife and six wonderful children, ranging in age from seven to fifteen. They are avid readers (to the point that we actually have to restrict their reading until *after* their homework was done!), and they particularly love fiction.
Curious about what they read, I would sometimes pick up a book they're reading. I've found that there is very little kid-/family-friendly fiction out there. Scenarios that -- at best -- would be R-rated would be played out page after page. So, I began writing for them.
The stories I write always are clean. There's no vulgarity, profanity, or sexual content. Some may say that's not the real world; I say that reality doesn't have to be that way. It's not in the Walton's little world. The purpose of each story is to entertain, enlighten, and show that you can have great fun without falling in the salacious trap that many authors regrettably fall into. When I write, I try to incorporate some Judeo-Christian values, and my hero in this endeavor is C.S. Lewis.
My plots are filled with action, but through encouragement from my oldest daughter (15), I have tried to be more descriptive. I enjoy integrating multiple subplots along side the main plot, and developing multiple characters. The reader will find that the villains are wonderfully awful -- you'll enjoy hating them. The protagonists are easy to empathize with as they try to be good while tripping over their shoelace. They do make mistakes and have to live through the consequences.
I hope this is not dismissing, but I wrote these books for my kids, really. Still, I would hope that you will enjoy them too.
When I was a teenager, I discovered computers (this was before the IBM PC days!), and I knew that would be career. I went to Brigham Young University and, later, University of Utah where I completed a Bachelors of Science, a Masters of Science, and a Masters of Philosophy in Computer Science. The intervening time was spent working for Hewlett Packard, Nationwide, American Electric Power, etc.
In 2001, SAMS Publishing gave me the privilege of writing a book for them called Linux Socket Programming. They were amazing, and I would write for them again in a heartbeat. It may sound strange, but I wrote this book for myself -- I wanted to create for myself a reference, but I knew that simplifying network programming would become essential for all network programmers. Another book written by Stevens was too academic for the typical programmer who was trying to meet a deadline. But, technical writing wasn't enough.
I have a beautiful wife and six wonderful children, ranging in age from seven to fifteen. They are avid readers (to the point that we actually have to restrict their reading until *after* their homework was done!), and they particularly love fiction.
Curious about what they read, I would sometimes pick up a book they're reading. I've found that there is very little kid-/family-friendly fiction out there. Scenarios that -- at best -- would be R-rated would be played out page after page. So, I began writing for them.
The stories I write always are clean. There's no vulgarity, profanity, or sexual content. Some may say that's not the real world; I say that reality doesn't have to be that way. It's not in the Walton's little world. The purpose of each story is to entertain, enlighten, and show that you can have great fun without falling in the salacious trap that many authors regrettably fall into. When I write, I try to incorporate some Judeo-Christian values, and my hero in this endeavor is C.S. Lewis.
My plots are filled with action, but through encouragement from my oldest daughter (15), I have tried to be more descriptive. I enjoy integrating multiple subplots along side the main plot, and developing multiple characters. The reader will find that the villains are wonderfully awful -- you'll enjoy hating them. The protagonists are easy to empathize with as they try to be good while tripping over their shoelace. They do make mistakes and have to live through the consequences.
I hope this is not dismissing, but I wrote these books for my kids, really. Still, I would hope that you will enjoy them too.
Customer Reviews
|
Share your thoughts with other customers:
|
||||||||||||||||||||||
|
Most Helpful Customer Reviews
15 of 16 people found the following review helpful:
1.0 out of 5 stars
Are Other Reviewers Using the Same Book?,
By
This review is from: Linux Socket Programming (Paperback)
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.
5 of 6 people found the following review helpful:
3.0 out of 5 stars
Has useful tidbits (but that's about it),
By
This review is from: Linux Socket Programming (Paperback)
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.
2 of 2 people found the following review helpful:
4.0 out of 5 stars
Very Good source and Explanation,
By slackware #1 (FtW,TX) - See all my reviews
This review is from: Linux Socket Programming (Paperback)
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 :^).
Share your thoughts with other customers: Create your own review
|
|
What Other Items Do Customers Buy After Viewing This Item?
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product).
|
Sell a Digital Version of This Book in the Kindle Store
If you are a publisher or author and hold the digital rights to a book, you can sell a digital version of it in our Kindle Store.
Learn more
