One of my challenges at work is to find a technology that will help "retool" AS400 developers to develop/migrate to web-based applications with a SOA/ESB service layer. We are looking at several frameworks and toolkits that fulfill this requirement. What I would like to know is from an architectural standpoint, does your book talk about the costs of ownership of using AJAX instead of the competing technologies in this space? Like others in on this forum, I have concerns about maintainability, performance, accessibility and security.
Foundations of Ajax will help demystify Ajax; some claim it's rocket science and frankly it's not. If you've developed web apps, I would say that adding Ajax doesn't dramatically change the equation of maintenance, performance, etc. There are a number of tools that we focus on in the last half of the book, things like Venkman, the DOM Inspector, etc. that are really help development. Perhaps showing reluctant developers those will convince them to convert.
Nate Schutta<br />Coauthor of <a href="http://www.amazon.com/exec/obidos/redirect?link_code=ur2&camp=1789&tag=ntschuttacom-20&creative=9325&path=tg/detail/-/1590595823/qid=1127567332/sr=8-1/ref=pd_bbs_1?v=glance%26s=books%26n=507846" target="_blank" rel="nofollow">Foundations of Ajax</a><br />My blog: <a href="http://www.ntschutta.com/jat/" target="_blank" rel="nofollow">Just a Thought</a>