A growing number of the 90,000 network programmers who bought Rich Stevens' UNIX Network Programming need to address a topic not covered by this classic--how to deal with Windows Sockets, also known as WinSock. This book is the defintive word on WinSock, offering a complete tutorial on how to work with Windows Sockets and sample code, which will be available on the Internet.
Customer Reviews, including Product Star Ratings help customers to learn more about the product and decide whether it is the right product for them.
To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. It also analyzed reviews to verify trustworthiness.
This books provides a very good overview of WINSOCK structure and functions for applications. However the book is not for someone who is looking for a SAMS type of step by step instruction. This book can be somewhat confusing.
While this book has a lot of good information, it is out dated, sometimes wildly so. It continually hampers itself with discussions of 16-bit Windows which, while still in use in 1995/1996, was clearly on the way out, contrary to what the writers assert in the first chapter. Having said that, it is well written and the book deserves a second edition, dedicated to Winsock2 with nary a word on 16-bit windows.
The coverage of WinSock basics in this book is quite good, but the book has an Achilles heel - it's sorely out of date, concentrates on the 16 bit model way too much, and has NO THREADED EXAMPLES AT ALL (async winsock work is covered entirely with message-based calls, on the grounds that this approach is portable to Win16 - like I care about that anymore). If you're interested in threaded Winsock work, then wait for a new edition or look elsewhere. If you're still writing for 16 bit Windows then (a) this book is fine for you, and (b) you have my condolences.
Although this book is focused on Windows and most of my (current) programming focuses on that, I usually end up referring to two UNIX books instead ("UNIX Network Programming" and "Advanced Programming for the UNIX Environment"). Those books have nearly identical syntax, but do a better job of explaining things. For Windows, there are some peculiarities (i.e., shortfalls) that you need to be aware of, so you really should own all three books, as I do. The amount of time that you save will be well worth it.
I am a very experienced C/C++ software engineer currently taking a community college class on WinSock networking programming. I'm used to dealing with difficult text books. However this is one of the worst I have ever wrestled with. There are no exercises in the book. All their examples are long; no short examples of code to clarify any topic. Their way of explaining most subjects seems to me to be unclear, their wording such that I have to read a paragraph several times to figure out what they are trying to say. Finally and especially, their explanation of the key topic of socket states is flat-out awful. I have had a little experience dealing tangentially with socket states on my last project, and I still came away from this chapter confused and with my head spinning. I hope that there are better WinSock books than this out there!