Reviews for Computer networking

The average rating for Computer networking based on 2 reviews is 3 stars.

Review # 1 was written on 2014-06-21 00:00:00 Janet Harrison This textbook was required reading for a Computer Networking course. As far as college textbooks go, it was pretty good. I learned the material from it that I needed to learn. The textbook was well-organized, and it was easy to understand. It had quite a few analogies and real-world examples that aided in understanding. For me, this textbook was a pretty dry read and I sometimes had trouble pushing through the weekly reading assignments. However, networks are not an aspect of Computer Science that I'm particularly interested in, so this was to be expected. I usually found the beginning of each chapter interesting, but my interest tapered off about halfway through and the rest was a chore to get through. However, I did learn a lot about how networks work. I may not retain all of the nitty-gritty details over the long term, but I expect the main concepts to stick with me. I think one of the best parts of this textbook were the Wireshark labs at the companion website, which my professor used for some of our assignments. I had fun learning how to "sniff packets", and I liked seeing the protocols in action for myself using real, live information being passed to and from my own personal network. Aside from my subjective complaint about the dryness of the material, my only other real complaint is in regard to the acronyms. There were an amazing number of acronyms, and many of them were not in the index so it could be difficult to find the original definitions again. Once an acronym was defined once, it was not defined again - at least not within the chapter in which it was introduced. (The chapters were 70-100 pages long.) A glossary of acronyms in the back of the book would have really helped. To any future readers of this textbook, I recommend making a note of each acronym you encounter and at least noting the page # where it was first introduced in case you need to reference its definition again.

Review # 2 was written on 2020-07-18 00:00:00 Albert Kiefer This was such a boring book. So much so that I would discourage anyone from picking ip up (or studying Computer Networking for that matter). First let me point out the characteristics that I liked most, so that I won't come across as a nuisance, and that prevented me from giving a lower rating - At anyone's reach - Very comprehensive prose, as far as the topics that the authors chose to cover are concerned (indeed, I felt much was left over) Now comes my critique: this book feels aimed at a five-year old audience! Paragraphs feel like a watered-down, wordy mass of text -- this gives clarity, but is boring as hell to read! I expected (if not demanded from a Computer Science course) more formalism, technical sophistication than what I got from two authors afraid of overwhelming their audience. Computer networking basics are covered satisfactorily, but the watered-down, romanticized prose prevented the text from achieving a thicker conceptual density; a book style more appropriate for students with an interest in industry-related applications than on insight and true understanding. I once had a talk with a networking tutor at my university, and he told me part of his work dealt with Markov's chains and probabilistic modeling; I read many of the end-of-chapter interviews, and the interviewees often remarked a conceptually richer footing for computer networking that this book expressed. Why wasn't any of all this covered in this text? Where did the cool stuff go? OK, I got a good grasp on the ISO/OSI stack -- up from HTTP, e-mail systems, P2P networks down to TCP congestion and flow control mechanisms, link-layer devices and LANs and basic network security notions (that was probably the part I liked most) but in the end I felt I was only acquiring passive knowledge with no reasoning involved. Is that a problem with this particular book? With computer networking? Worse yet, for computer science courses in general? Additional flaws - Ridiculously over-priced hard-cover copy (I borrowed one from the library) - No solutions for end-of-chapter exercises (not even wireshark) - Questionably ugly top-down approach. Makes one feel like applications deserve more attention than theoretical understanding