Professional Ajax

EBook Description: provides a developer-level tutorial of Ajax techniques, patterns, and use cases. The book begins by exploring the roots of Ajax, covering how the evolution of the web and new technologies directly led to the development of Ajax techniques. A detailed discussion of how frames, JavaScript, cookies, XML, and XMLHttp requests (XHR) related to Ajax is included. After this introduction, the book moves on to cover the implementation of specific Ajax techniques. Request brokers such as hidden frames, dynamic iframes, and XHR are compared and contrasted, explaining when one method should be used over another. To make this discussion clearer, a brief overview of HTTP requests and responses is included. Once a basic understanding of the various request types is discussed, the book moves on to provide in-depth examples of how and when to use Ajax in a web site or web application. Different data transmission formats, including plain text, HTML, XML, and JSON are discussed for their advantages and disadvantages. Also included is a discussion on web services and how they may be used to perform Ajax techniques. Next, more complex topics are covered. A chapter introducing a request management framework explores how to manage all of the requests inside of an Ajax application. Ajax debugging techniques are also discussed. The last part of the book walks through the creation of two full-fledged Ajax web applications. The first, FooReader.NET, is an Ajax-powered RSS reader. The second, called AjaxMail, is an Ajax-enabled email system. Both of these applications incorporate many of the techniques discussed throughout the book.

AJAX is an exciting Web platform for many reasons. Using AJAX, many tasks that were traditionally performed on the server happen in the browser instead, resulting in fewer round-trips to the server, lower bandwidth consumption, and faster, more responsive Web UIs. While these outcomes are the result of offloading a good deal of work to the client, the browser still isn’t the environment of choice for many developers who would rather have the full power and flexibility of server apps at their disposal.

Ajax Patterns and Best Practices

Ajax Patterns and Best Practices

Ajax is taking us into the next generation of web applications. Ajax has broken the client-server barrier by decoupling the client from the server, but an Ajax application still needs a server to extract content from. The most effective use of Ajax and the server requires an understanding of REST, an architectural style used to define Web services.

Ajax Patterns and Best Practices explores dynamic web applications that combine Ajax and REST as a single solution. A major advantage of REST is that like Ajax, it can be used with today's existing technologies.

This is an ideal book whether or not you have already created an Ajax application. Because the book outlines various patterns and best practices, you can quickly check and verify that you're building an efficient Ajax application.

Inside the book, the patterns will answer the following questions:

* What is Ajax, and REST and why do you even care? And if I should care what are some examples of websites that make effective use of Ajax and REST?
* What are the absolute basics of Ajax and REST and what parts of those basics should I use?
* How should deal with large amounts of data? Should I cache the data? Should I get the data piece fed to me? (Patterns: Cache Controller, and Infinite Data)
* People keep telling me that sessions and cookies are bad? Are they bad? What should I do? And while I think about how about generating content for other devices? (Permutations pattern)
* I want to fix the back-button problem of the HTML browser. (State Navigation pattern)
* What is the best way to create a mashup? (REST Based Model View Controller pattern)
* My page has so many links managed by JavaScript, and I am loosing control, help me make this more organized! (Decoupled Navigation pattern)
* I understand that HTTP means I send data to the server, how about the server sending me some data without asking for it? (Persistent Communications pattern)
* My server side code looks like a mess with tags and code pieces everywhere how can I organize and make my HTML page behave like a SOA client and use REST based web services? (Content chunking pattern)

• Free IAS eBooks
• Free GRE eBooks
• Free MBA eBooks
• Free GATE eBooks