Atm: Theory and Application (Mcgraw-Hill Series on Computer...

Features

• Cover Type: Hard Cover with 324 pages
• Published by: Mcgraw-Hill Tx September 1994
• Written in: English
• ISBN 10 Number: 0070603626
• ISBN 13 Number: 978-0070603622
• Book Dimensions: 8.9 x 6.1 x 1.2 inches
• Weighs: 1.9 pounds

Reader Reviews
This review is from: ATM Theory and Applications (Paperback) I turned to this book to understand how the various ATM functions work. I had quite a bit of both practical and conceptual networking background prior to opening this book. As such, I've read quite a number of good and bad technical books on various networking topics. If you'd rather not read the rest of this review here's the gist. Don't buy this book. Instead, buy Oliver C. Ibe's 'Essentials of ATM Networks and Services'. After you've mastered that, use Mark Miller's 'Analyzing Broadband Networks' to see how ATM Layer PDUs are put together and exchanged in various situations like call setup/teardown etc. Here's the rest of the review. Within minutes of reading, I got that old My-Head-Is-Swimming feeling. Not because I couldn't understand what the authors were saying, but more so because I couldn't figure out why on earth I was reading stuff that was irrelevant. Here are a few cases in point: Every ATM book I've thumbed through religiously talks about the B-ISDN model. And when it starts explaining how something in ATM acutally works (say SSCOP), there is no reference to any of the terms that were introduced and defined in talking about the B-ISDN model. Why talk about the model at all then? This book is no exception. The vast number of initial pages (285 in fact!) dedicated to talking about things like X.25, FR, multiplexing schemes etc. are useless. If you don't know this stuff, you have no business reading a book dedicated to ATM. And if you're just learning this stuff, there's no way you're going to really understand ATM. And of course, these authors couldn't resist the whole 'business drivers for ATM' nonsense. The only redeeeming part about the book was Chapter 25 on Traffic Engineering. Just goes to show what technical authors can do when they're talking about stuff they know really really well. This is also the chapter where the authors use language relatively more precisely and concisely - a rare blessing in this overall tedious and pompous book. Someone ask these guys to check out (...)! Comment | | (Report this)