Rating: 
Summary: buy it even if you own Stevens' book
Review: This book has a perfect balance of brevity and depth. Anything shorter would have been superficial, anything deeper would begin to compete with Stevens' Unix Network Programming (and lose). As is, this book fits very well for developers who do occasional TCP/IP development, but still need to develop reliable, industrial-grade software.
Rating:
Summary: A must have book for network programmers
Review: This book is a must book for newsockets applications writers. The book gives the basics of TCP/IP for programmers, rather than from an academical point of view, giving effective tips, techniques, and whole programs in C to assist network programmers in writing solid networking programs.
Rating:
Summary: Lives upto its name
Review: This book is one of the few you would like to have in your library.
a. It compresses the TCP/IP working in short and sweet format.
b. It's tip section has lot of sub tips/information which mention differences/workarounds etc in concise way.
c. It has extensive hands on samples to refer to.
d. It feels like culmination of real life hands on implementation of protocol suite and its usage in day to day life which author succintly conveys to readers in form of anecdotes/ideas etc.
e. Author is very precise about what book is not and thus maintains the readable/digestible size of the book and refers to comer/steven when appropriate.
f. It will be useful for every software eng to understand the workings and sometimes even pick cool concepts from the most scalable app ever designed (TCP/IP).
Overall the best book buy...most of the effective series have been good.
Rating:
Summary: A MUST HAVE BOOK
Review: This book provides an excellent insight into TCP/IP programming. The concepts are presented in a system independent manner as much as possible. The focus of the book is to teach TCP/IP programming concepts and not to teach how to program in WINDOWS, so readers who are not competent in Windows programming may need another reference to help them out there. I have not found another book that so clearly outlines the considerations that must be made in order to design an effective and robust TCP/IP interface. A list of some of the points that I found very helpful are:
1) Why to use TCP instead of UDP except for very specific circumstances.
2) TCP is a STREAM protocol with no inherent notion of message or message boundary.
3) Why to combine data into larger writes instead of many small writes.
4) A discussion of avoiding movement of data with Shared Memory.
Rating:
Summary: A MUST HAVE BOOK
Review: This book provides an excellent insight into TCP/IP programming. The concepts are presented in a system independent manner as much as possible. The focus of the book is to teach TCP/IP programming concepts and not to teach how to program in WINDOWS, so readers who are not competent in Windows programming may need another reference to help them out there. I have not found another book that so clearly outlines the considerations that must be made in order to design an effective and robust TCP/IP interface. A list of some of the points that I found very helpful are:
1) Why to use TCP instead of UDP except for very specific circumstances.
2) TCP is a STREAM protocol with no inherent notion of message or message boundary.
3) Why to combine data into larger writes instead of many small writes.
4) A discussion of avoiding movement of data with Shared Memory.
Rating:
Summary: A MUST-HAVE for Programmers and Sysadmins!
Review: This is a "best of class" book. Jon Snader's explanations are stunningly lucid and his sample code can be plucked out and used repeatedly. If you have ANY need to understand TCP/IP programming -- whether you program or manage a network -- you will love this book. It's one of the few that I'll read cover to cover, maybe even more than once! One of the very best books in my extensive library!
Rating:
Summary: read it
Review: This is one of the few tcp/ip programming books I know that dares to go under the inner workings of the socket interface. Thus, it provides valuable information for using sockets in a reliable way. Certainly the definite reference is Steven's "Unix Network Programming" vol I (I have not checked out yet Comer's book vol III Linux version).
| 
