Ebook: Developing Service-Oriented AJAX Applications on the Microsoft Platform

Someone in the review stack has written that after reading you will hate AJAX, WCF and SOA. That's very true - and I read only three chapters! It is written in a very contrite and dull manner, and after reading few chapters your eyelids start to droop. Coming to the technical side, he gets data from the database throgh WCF, and use complex javascript and XSLT coding to display data on the aspx page. Is it not beating the purpose of n-tier architecture, where all the business logic should be in the business layer and the aspx page should simply display the data without much scripting or code? To display data in a gridview you simply drag the control and bind the data with a few lines of code. But according to the methods described in the book, you have to write lines after lines of scripting to display the data. WHY? This book may be OK, after you have a good understanding of SOA and WCF, and somehow enjoy writing several lines of scripting to display data.