Internetworking with TCP/IP, Vol. III: Client-Server Programming and Applications

[gerard4143]

Hi,

I'm really thinking about purchasing this book - Internetworking with TCP/IP, Vol. III: Client-Server Programming and Applications, Linux/POSIX sockets version by Douglas Comer - but I have a few concerns...

1. Its the third is a series and I haven't read the first two, will this make the book hard - impossible to understand?
2. I already read - Unix Network Programming, The Socket Networking API Vol 1 3rd Edition by WR Stevens and company. Now I found most of this book very understandable but at the same time found the latter chapters more of and after thought(especially the information after chapter 11). Would you consider it a waste of money to purchase this book considering the amount of material that would be repeated?

I'm really looking forward to expanding my small programming library but I would also like to get the most bang for my buck. If you have any info on the above book could you please pass it on...Thank-you Gerard4143

[Thrillhouse]

I don't have Vol. III but I do own Vol. I as we used it in grad school for a Network Security course. So, I can't comment on the quality of the text, itself, nor can I comment on the amount of material repeated between it and the other book you mention, but I can tell you that you shouldn't have any trouble with only owning Vol. III as each book seems to be completely self-contained (e.g. Vol. I never referred to material in Vols II or III so I would assume it's the same for each book in the series). I think the only reason you would need Vols I or II would be as a reference for the details of the various TCP/IP protocols. So if you already have a good understanding of them (or some other book you can use as a reference), I would say you'd be safe to only purchase Vol. III.

[Rubberman]

All three volumes have a prominent place on my programming book shelf. I think that not only should you have all of them, but you should also get the DOD white book - DDN Protocol Handbook. I have vols 2-4, though they are really useful only if you are either writing TCP/IP protocol support from scratch, or trying to debug a protocol stack that doesn't seem to be working properly. I have them because in my deep, dark past I had to implement an entire TCP/IP stack (including Berkeley libraries) from scratch. Truly a joyful experience, NOT! It would have been impossible to do so without the DDN handbooks, and the use of Comer as to proper behavior of the Berkeley TCP/IP C library functions.

[gerard4143]

Thank-you for the replies.

I did some looking around checking out reviews and the enclosed code that comes with the book and I made the plunge. I just purchased the book and in about 1 - 2 weeks it should be arriving...I hope the level of the book isn't too overwhelming(Thrillhouse mentioned that he used one of the series for a graduate course). As for the other two in the series Rubberman, I'll see how this one goes...Again Thank-you for the replies Gerard4143

[gerard4143]

I found this quote from the author which answers my question about the previous volumes:

"Although this volume can be read and used alone, it forms part of a larger picture completed by two other volumes in the series. Volume 1 considers the question "What is a TCP/IP internet?" Volume 2 examines the question, "How does TCP/IP software work?" It presents more details, examines working code, and explores greater depth than the first volume. Thus, although a programmer can learn to create network applications from Volume 3 alone, the other volumes can be used to provide a better understanding of the underlying technologies."

So I guess its recommended but not necessary which is a relief.

[Rubberman]

I know that these are expensive books. Get what you can afford, and budget the others for when you have some spare $$. As a whole, the 3-volume set is one of the masterworks of software engineering, and still timely almost 20 years after publication. Similarly, another set to have is Knuth's The Art of Computer Programming. If you don't have any other books on the shelf, these two sets along with Wirth's Algorithms + Data Structures = Programs, Kernighan & Ritchie's The C Programming Language (K&R), and Ellis & Stroustrup's The Annotated C++ Reference Manual (the ARM) are the essentials for professional software engineers. There are more that one should have, especially the "Gang of Four"'s Design Patterns, and Scott & Fowler's UML Distilled to help cover current trends in software engineering, but the aformentioned works are essential and will teach you more of the essentials than 4 years of programming classes at the university.

[gerard4143]

Thanks for the list of books Rubberman, have them saved and will be checking them out...Gerard4143

[Rubberman]

Say hello to Anne of Green Gables for me, should you run into her! And happy New Year!

[gerard4143]

Say hello to Anne of Green Gables for me, should you run into her! And happy New Year!

See only comes to life in the summer musicals and its so winter right now...Gerard4143...Happy New Year Rubberman

[gerard4143]

Well the book finally arrived...first impressions(chapters 1 - 3).

Its well written, planned and has a fundamental purpose of exposing TCP/IP applications to the developer. I have to say I'm very surprised at how readable this book is an enjoyment so far.

Note - The book does assume C programming knowledge and experience with the Linux OS system..