<< 1 >>
Rating: 
Summary: NOT WORTH THE MONEY
Review: I bought this book in hopes in would help me understand dhcp for the mcse exams. Well, I was wrong. $45 down the drain. This book has no more information than any of the other tcp/ip books on the subject of dhcp. Dont let the dollar price fool you into thinking your getting a good book. Needless to say, I was very disappointed in this book.
Rating: 
Summary: Great Content, Lousy Editor
Review: I purchased this book on the way to the airport in transit to yep, fixing a distributed DHCP server problem. I found a great deal of useful information in the book, and after having read the book, I am considered an expert among most mortals. The book successfully turns the RFCs on the subject into readable text, and liberal use of footnotes are there to explain some of the more esoteric notions, and shows packet formation, which is a valuable visual aid. Unfortunately, I also found an unacceptable number of editing errors. Kercheval (author) has done a very good job with presenting the information, but the editor missed a lot. The book was edited by Radia Perlman (says so on the back cover), and I have to say if I see his/her/its name on other books as editor, I'll have to pass. This book has a lot of usefulness in it, but the errors in editing are glaring if you know anything at all about networking. Normally, I wouldn't be too upset about typos, but in technical works one wrong character can change the entire meaning of whatever point is being made. My technical writing professor in college would have flunked this editor in a heartbeat. I forwarded a list of my concerns to both the author and the publisher. Kercheval was interested in them, the publisher did not fill my heart with warm fuzzies, or even acknowledge receipt. A simple "Thank You" would have been nice. A next edition with the corrections would be fantastic. If you want the guts of DHCP, and you need it now, go ahead and by this edition. If you can wait til Prentice Hall gets it right, then buy the next edition. Personally, if I were Kercheval, I'd be majorly P.O.ed... Can you sue a publisher for malpractice?
Rating:
Summary: save your money !
Review: There is no depth, and the writer constantly sits on the fence during technical discussion. Additionally, there is no information regarding how specific packages deploy the protocols.
<< 1 >>
| 
