Because Ajax moves so much application logic from the server to the client, it forces many developers to master a wider range of web technologies than ever before. To work effectively on Ajax projects, front-end developers have to concern themselves with database performance, business logic and other server-side concerns. Back-end and middleware developers, meanwhile, have to make friends with XHTML, CSS, JavaScript and a wide range of browsers. Sure, it’s possible to develop Ajax apps in a siloed team environment. But it’s not the easiest way, and it rarely provides the strongest results.
Shawn M. Lauriat’s “Advanced Ajax: Architecture and Best Practices” (Prentice Hall, 2008, 360p) bridges the gap between developers with exclusive client- or server-side skills. By exploring tools, technologies and best practices for every layer of the Ajax programming model, this solid new programming manual promises to plug the holes in any developer’s resume. Lauriat’s tops-to-tails approach offers something for almost any developer, but it also guarantees most readers will find some sections remedial. As this two-part review will demonstrate, that’s not necessarily a liability.
This week I’ll examine the book’s first four chapters, which focus almost exclusively on the client-side technologies that are my own personal speciality. Next week I’ll examine the remaining chapters, which move further down the technology stack to explore server-side concerns.
Lauriat’s announces his goals early, shortly after pointing out the introductory nature of many existing Ajax books and tutorials:
This book, instead, looks at using Ajax to create rich, browser-based interfaces for enterprise-level web applications, taking into account the flexibility, reusability, scalability, and maintainability necessary for such an undertaking. Ajax does not exist in this book as the latest and greatest acronym to hit web development. It instead exists as a tool like any other – extremely useful in some instances and totally wrong in others.
This focus on Ajax as a means rather than an end continues in the author’s examination of user-focused application design:
Ajax-based functionality fits best where it makes a given task easier for the user, rather than just replicating functionality easily achieved by simpler, faster-developed means. Using half a dozen JavaScript files, numerous CSS files, and several Ajax calls just to render a company home page uses a lot of time and memory for very little benefit to the user.
Having established his mission statement, Lauriat dives right into the specific technologies and approaches that client-side Ajax demands. He makes the case for semantic markup, web standards, progressive enhancement and accessibility in a way that should compute for server-side developers who may be encountering these concepts in depth for the first time. “Advanced Ajax” doesn’t tackle these concepts to the level that, say, Jeffrey Zeldman would, but Lauriat doesn’t scrimp on the real-world details. He provides compelling examples of the way high-contrast design, resizable page layouts, easily targeted controls and even the draft ARIA spec can enhance accessibility and usability for everyone, not just disabled users.
Once he’s covered the basics of how to use client-side technologies appropriately, the author examines the specifics of client-side architecture. He explains JavaScript’s object model and prototype-based inheritance with the appropriate level of detail for programmers better versed in Java or other server-side languages. Extensive code examples eschew jQuery and other Ajax frameworks, allowing readers to understand the nuts and bolts of cross-browser JavaScript development. Here, again, Lauriat displays a knack for providing neither too little nor too much detail. He discusses design patterns and strategies for abstraction just like he discusses Ajax itself: as tools rather than mandates. Readers with previous exposure to MVC architecture and event-driven programming should gain a better understanding of those techniques. Novices, meanwhile, should learn enough to understand the code samples and perhaps find their curiosity piqued for further study.
Having covered client-side technologies and architecture, Lauriat finally turns to development and debugging tools. Validators, browser consoles and plug-ins, profiles and unit-testing frameworks all get their due. Here, as elsewhere, Lauriat delves into the nitty-gritty of developing applications for IE, Safari, Firefox and Opera. He suggests tools and techniques for each browser environment without getting into political asides. As with the earlier chapters, I came away with a more complete, holistic understanding of topics in which I already considered myself well-versed.
Taken as a whole, the client-focused chapters of “Advanced Ajax” are worth skimming even for senior client-side developers. For programmers just getting acquainted with the UI layer, these chapters provide an extremely concise, yet thorough treatment of a huge number of important topics. I’m extremely impressed with Lauriat’s book, and I haven’t even gotten to the sections that will cover the most new ground for me personally. Next week, in part 2, I’ll examine chapters on everything from security and database optimization to server-side architecture and game development.
