Product Description

Product Details

• Amazon Sales Rank: #33626 in Books
• Published on: 2008-01-01
• Original language: English
• Number of items: 1
• Binding: Paperback
• 957 pages

About the Author
Anthony T. Holdener III currently builds Internet/Intranet applications utilizing the latest available technologies while striving for accessibility and cross-browser compatibility. He has worked with the web in one form or another since 1997 when he helped open an Internet cafe in Fairview Heights, Illinois. A graduate of St. Louis University with a degree in Computer Science, Anthony has worked as a web architect or developer for the past eight years for a number of Fortune 500 companies in the St. Louis area.

Customer Reviews

Loads of Code; Good Value
§
There is a LOT of code in this 950 page book. I guess there is something here for everyone because there is code not directly related to Ajax but is directed to HTML structure or CSS presentational aspects or to frameworks that may include Ajax conveniences.

In fact, the amount of code may interfere with the author's object of appealing to two very different types of people with this book: Web developers and project managers looking for a high-level view. Except for some intro chapters and the odd breather between 10-15 page code listings, I don't think any project managers *I* have worked with would extract much from the book.

The book has 4 sections:
Part 1 - Ajax Fundamentals: the basic technologies that could form the core of a typical Ajax application.

Part 2 - Ajax Foundations: approaches to standards-compliant structure, separation of the presentational layer and client-side behaviors. Code code code!

Part 3 - Ajax in Applications: describes the specific implementations of these technologies into Web applications. More code!

Part 4 - Wrapping Up: tips on optimization.

In addition, there are some reference appendices on XML and XSLT; on JavaScript frameworks; on Ajax implementation risks; and most interestingly, a catalog of freely available Web service APIs.

One thing I did not like about the code listings was the use of Prototype style $() function syntax. This means when I see something like:
var titleText = $('title').firstChild;
I had to check whether .firstChild was a reference to a Prototype object or a reference to the standard DOM object. If the standard object, it would have been a whole lot clear just to have written document.getElementById().

The book index is actually pretty good. With 950 pages stuffed with content, you will probably be thankful for that!
§

Exhaustive but flawed
While "Ajax: The Definitive Guide" is certainly exhaustive, it's hard to have confidence in a text so riddled with errors. Other O'Reilly titles I've purchased in the last few years suffer from the same problem: very poor copy editing. In a "Definitive Guide," this is inexcusable.

Furthermore, he author's decision to rely on the Prototype framework is misguided. It saves a few lines of code per page, but one expects a "Definitive Guide" to define, explore, and use the actual objects and methods defined by the language itself, not those defined in one of many, many external libraries.

It is also somewhat comical to read on page 10 that developers, rather than browser vendors, "are to blame for not adopting standards" and that they are "stuck with the mentality of the 1990s, when browser quirks mode, coding hacks, and other tricks were the only things that allowed code to work in all environments," and then to read on page 191 that "Yes, there are always caveats in the world of standards compliance" and that "Example 7-2 will not work in Internet Explorer because Internet Explorer does not support the CSS2 rules that are used to make this work." And on page 187 that "Internet Explorer does not natively support :hover on elements other than . For this reason, instead of using the CSS that will work for all other browsers, we must use this...."

(It's hard not to laugh, too, at a sentence that begins with "To take the file menu example fully to the Web 2.0 level....")

By the time all the errata are corrected and a second edition issued, it might be appropriate for the author to wag his finger at developers who can't yet afford to to be totally standards-pure, but by then the faddish jargon will seem very dated.

And until O'Reilly starts employing copy editors, I'm not buying the first edition of any title they release.