[.ca] Unix Network Programming, Volume 1: The Sockets ... (ISBN 0131411551)

LUG:ng Book review:
The book was great. It covers both the basics for the TCP/IP API in Unix and some advanced techniques of Network Programming. The book was a very easy read and flowed great. There were plenty of code examples so you could read and see how the functionality would work. Besides this being a great reference tool for any Unix Programmer, it is a great tool for anyone looking to develop Unix apps with the new IPV6 standard. The book thouroughly covers both IPV4 and IPV6. When using it as a reference tool, the index is amazingly detailed. It makes finding the information your looking for quick and easy. This is one book that a Unix Programmer can't do without.

Invaluable UNIX Programming Resource:
While not a C programmer by any means, I decided to take some time and tackle the UNIX Network Programming book. I found that lots of early college classes came back to me as I forged a few pages in. It was clear from the very beginning that this book was going to be a very detailed study on all aspects of IP networking as it relates to UNIX programmers. Even for someone who isn't initiated in the topic or really even interested, it was quite an experience to read through the hundreds of flow charts and detailed examples of C code showing how to perform all kinds of interesting network tasks. From a simple HTTP GET to detailed network file and connectivity operations, including TCP and UDP packets, ports, sockets and so on, there is a place in the book for each kind of network programming service. There is also a fair amount of text dealing with debugging techniques, allowing even those programmers who are experienced in their craft to find new ways to ferret out the problems in their code. The book also promotes good stylistics in programming, engendering the idea that readable and understandable code is better code than that which simply works. There are also examples and explanations for IPv6?, for any programmer who is going to be making the leap into next generation networks. There are also instructions on how to deal with wireless networks, security models and other topics for anyone who plans on designing network applications or specialized network configurations. It's probably not accurate to rate a book on a topic that holds little interest to the reader, but even a modest script programmer can tell when a book hits a subject just right and brings out all the details in a concise, easy-to-understand way. If you're a hard-core network programmer, this book is definitely for you. If not, you may find you learn something anyway.

Great book, while code exmp could be more straight forward:
I bought this book about a month ago and used it very extensively for my UNIX programming project. While this book is great and very comprehensive, I did find code examples very confusing. As coping a variable from the socket struct into variable and then from this variable into custom structure, then manipulating this custom structure and finally printing. It would be better to use as less transformation as possible. Because it makes very hard to find what this variable has and where it came from. At the end all I'm looking for is simple but good example of how to use sockets...etc, it's not a C programming book.

Continuing the work of a legend in the field of CS:
It would be difficult to put value on a book that has been a classic text and a reference in academia and in the real world in the context of Network Programming for over a decade. Richard Stevens published the ever-popular Unix Network Programming \oUNP\c back in 1990, followed the second edition in 1998. With a dedication to the memory of R. Stevens, the UNP book found itself two new authors, Bill Fenner and Andrew M. Rudoff, who would write the third edition of this book. The third edition has many updates, a new look and feel and many of new chapters that cover the topics more applicable these days. In my opinion, it is still the most valuable and profound text in the context of Network Programming. For those of us who have the first two editions of this book, the third edition has the following changes in effect: · IPv6 updates. In the second version of the book, IPv6 was merely a draft and the sections covering IPv6 has been updated to take these changes into effect. · POSIX updates. The functions/APIs and examples have been updated to reflect the changes to the latest version of the POSIX specification (1003.1-2001) · SCTP coverage. 3 new chapters that cover this new reliable, message-based transport protocol have been added. · Key Management Sockets coverage. Network security and its applicability and use with IPsec. · Updated Operating Systems and machines that are used to run the examples in the book. · Some topics such as Transaction TCP and X/Open Transport Interface have been dropped. Many topics and sections have been updated with the authors' comments. These comments even though simple for someone new to the profession, are extremely useful as they are like hints and tips from one developer to the next to help you out in your next programming assignment. If this is the only edition of the book that you are reading, you are in for a treat. Topics in Network Programming are covered in detail and using concrete programming examples that all of us can relate to - all Unix, but what else is there?! All kidding aside, the topics are covered well enough that they are useful information under any Operating System. The concepts don't change; sockets are sockets under any Operating System. The function call is different, but one needs to go thru the same steps under any environment. Being the most popular networking protocol, TCP/IP is covered in Part I of the book. One needs to have prior understanding of the TCP/IP protocol and the OSI model, however. If this is the first time you are looking at the programming aspects of networking protocols, Part I of this book will cover the basics. It starts you off with a couple of simple examples such as daytime client and a daytime server and it builds on that as the reader reads along. TCP, UDP and SCTP (Stream Control Transmission Protocol) are covered in brief in Part I, and basic concepts such as the three-way handshake of TCP and the four-way handshake of SCTP are depicted. Part II of the book covers sockets and socket programming. Topics such as the socket Address Structure in IPv4 and IPv6 for TCP, UDP and SCTP are covered and examples (the same daytime client/server) are given to convey the point to the reader. It is important to mention here that all the topics and concepts are depicted for the three transport protocols: TCP, UDP and SCTP. Every single socket API under the Unix programming environment is covered and examples are given for each function call to show the reader how the function can be utilized. An entire chapter has been dedicated to Socket Options and how they are used/can be used for best results. Hints are given throughout the chapter to tell the user about the pitfalls and best practices of each option. After the basics have been covered, various I/O models are depicted in detail and examples are shown to convey the pro's and con's of each I/O model. The five I/O models used thru the book and available under the Unix environment are: · Blocking I/O · Non-blocking I/O · I/O Multiplexing (using select and poll) · Signal driven I/O · Asynchronous I/O SCTP - Stream Control Transmission Protocol, a new IEFT standard are covered in later chapters of 9 and 10 and again in chapter 23. The two interface models of SCTP (one-to-one and one-to-many) are covered in detail, and their differences with TCP are also explained in full. The client/server example that has been used throughout the book is ported to use the new SCTP protocol. The authors then go into great detail explaining the problems that SCTP solves over TCP and where and how it would be useful to use SCTP. Advanced topics such as IPv4 and IPv6 portability, Unix Domain Protocols, Multicasting and advanced Socket programming for UDP, TCP and SCTP cover the rest of the chapters in this book. Various options for interoperability between IPv4 and IPv6 start off the last section of the book. A chapter on Advanced I/O functions brings the reader a new perspective of how complicated Network Programming can become. Non-blocking I/O, befits and examples are covered in chapter 16. The topics on Multicasting, and adding reliability to UDP are probably my favorite chapters in this book. The Time Server that has been used throughout the book is re-coded to become a multicast application. Some issues that arise when designing multicast applications such as multicast on a WAN are also discussed. The third edition of the UNP book is as good as ever. The updates truly reflect solutions to today's challenges in Network Programming. Bill Fenner and Andrew Rudoff did an amazing job continuing the work a true legend in the field of Computer Science.

A great teacher; an essential reference:
I learned both network programming and threaded programming (pthreads) from this book (the 1998 2nd edition), and it was a great teacher. I used it to design and implement a client server protocol for a research project involving 10 machines and about 15 communicating processes. One of the things I really appreciate about the book is the detailed examples. After the concepts (a server 'listens' for a connection; a client initiates a connection) and basics of packets and sockets, the book presents a simple tcp server and client -- the server simply echos back whatever the client sends. Next, it discusses what can go wrong with the simple version, and presents an improved echo server that behave better when the client crashes (and likewise an improved client). The book continues to improve on the basic client/server, including address resolution, and servers that handle multiple clients using forks, threads, non-blocking I/O. This is all I needed to learn from the book, and it's all in the first half of the book. Particularly useful is Chapter 27, Client-Server Design Alternatives. To me it alone was worth the price of the book. Here the book discusses concurrent servers with three basic architectures: (1) non-blocking I/O, no threads or forks (advantage: full control of resource allocation; disadvantag: complexity); (2) spawn a thread or fork for each client (simplest implementation; potential problem of too many children); (3) servers that pre-allocate a pool of threads or forks (a happy medium; faster). Other chapters discuss broadcasting, multicasting, out of band data, routing sockets, and raw sockets; all topics I hope to learn some day. Again, this is a great book. The 3rd edition brings it up to date for IPV6 and numerous small improvements.