book

Ajax Patterns and Best Practices

Name: Ajax Patterns and Best Practices
Author: Christian Gross
ISBN: 9781590596166

by Christian Gross

February 2006

Intermediate to advanced

410 pages

11h 44m

English

Apress

Read now

Unlock full access

Copyright
About the Author
About the Technical Reviewer
Acknowledgments
Introduction
What's My Vision of Ajax?Book and Pattern Road Map
1. Introduction to Ajax
1.1. Pictures Are Worth a Thousand Words1.2. Another Ajax Example1.3. Ajax Architecture Basics1.3.1. It's About the Data1.3.2. It's About the Navigation1.4. Comparing Ajax to Other Application Types1.4.1. Rich-Client Local Installation1.4.2. Rich-Client Web Services1.4.3. Plain-Vanilla Web Application1.5. Some Final Thoughts
2. The Nuts and Bolts of Ajax
2.1. Ajax for the Impatient2.1.1. Understanding REST Theory2.1.2. Implementing the REST Data2.1.3. Implementing the Ajax Application2.1.4. Putting Together Ajax and REST2.1.5. Understanding the Ramifications of Ajax and REST2.1.6. XMLHttpRequest Details2.1.7. Using the Factory Pattern2.1.8. Defining an XMLHttpRequest Factory2.1.9. Rewriting the Ajax Application to Use a Factory2.2. Making Asynchronous Requests2.3. Making Practical Use of XMLHttpRequest2.3.1. Implementing an Asynchronous Calling Mechanism2.3.2. Calling Domains Other Than the Serving Domain2.4. Some Final Thoughts
3. Content Chunking Pattern
3.1. Intent3.2. Motivation3.3. Applicability3.4. Associated Patterns3.5. Architecture3.5.1. Implementing Order in a Web Application3.5.2. Defining the Content Within a Content Chunk3.6. Implementation3.6.1. Implementing the HTML Framework Page3.6.2. Injecting Content by Using Dynamic HTML3.6.3. Understanding the Special Nature of innerHTML3.6.4. Binary, URL, and Image Chunking3.6.5. JavaScript Chunking3.7. Pattern Highlights
4. Cache Controller Pattern
4.1. Intent4.2. Motivation4.3. Applicability4.4. Associated Patterns4.5. Architecture4.5.1. HTML and HTTP Cache Directives4.5.2. HTTP Expiration Caching Is a Bad Idea (Generally)4.5.3. A Better Approach: Using HTTP Validation4.5.4. Some Findings Regarding Server-Side Caching4.5.5. Defining Static HTTP Validation4.5.6. Defining Dynamic HTTP Validation4.6. Implementation4.6.1. Implementing the Passive Cache4.6.2. Implementing the Server Side of the HTTP Validator4.7. Pattern Highlights
5. Permutations Pattern
5.1. Intent5.2. Motivation5.3. Applicability5.4. Associated Patterns5.5. Architecture5.5.1. Understanding Why the Resource Is Separated from the Representation5.5.2. Using Cookies and HTTP Authentication to Authorize Access Only5.5.3. Using Cookies5.5.4. An Example Book Application5.6. Implementation5.6.1. Rewriting URLs5.6.2. An Example Shopping Cart Application5.7. Pattern Highlights

6. Decoupled Navigation Pattern
6.1. Intent6.2. Motivation6.3. Applicability6.4. Associated Patterns6.5. Architecture6.6. Implementation6.6.1. Implementing the Action Functionality6.6.2. Defining and Implementing the Common Data Functionality6.6.3. Implementing the Presentation Functionality6.6.4. Using HTML Components6.7. Pattern Highlights
7. Representation Morphing Pattern
7.1. Intent7.2. Motivation7.3. Applicability7.4. Associated Patterns7.5. Architecture7.5.1. Basic Theory7.5.2. Why the Pattern Is Not an HTML Component7.5.3. Defining Blocks of State7.6. Implementation7.6.1. Implementing the Framework7.6.2. Implementing the Representation Reference Points7.6.3. The Details of a JavaScript Representation Reference Point7.6.4. The Details of an XSLT Representation Reference Point7.6.5. Some Implementation Details7.7. Pattern Highlights
8. Persistent Communications Pattern
8.1. Intent8.2. Motivation8.3. Applicability8.4. Associated Patterns8.5. Architecture8.5.1. Why the Internet Is "Broken"8.5.2. Implementing a Polling Solution8.6. Implementation8.6.1. Example: A Global Status Resource8.6.2. Implementing the HTML Page8.6.3. Implementing the ClientCommunicator8.6.4. Implementing the ServerCommunicator8.6.5. Calling the ServerCommunicator Intelligently8.6.6. Implementing the Server-Side Monitoring Process8.7. Example: Presence Detection8.7.1. Authenticating the User8.7.2. Updating the ServerCommunicator8.8. Example: Server Push8.8.1. Some Thoughts on Specifying URLs8.8.2. Using a Hard-Coded URL8.8.3. Specifying a URL by Using User Identification8.8.4. Specifying a URL by Using HTTP Redirection8.8.5. Completing the ServerCommunicator8.9. Version Numbers and Updates8.10. Performance Considerations8.11. Pattern Highlights
9. State Navigation Pattern
9.1. Intent9.2. Motivation9.3. Applicability9.4. Associated Patterns9.5. Architecture9.5.1. Moving Toward an Ideal Solution from the User's Perspective9.5.2. Extending the Solution for a Web Application9.5.3. Managing State at the Protocol Level9.6. Implementation9.6.1. Processing the Requests on the Client9.6.2. Processing the Requests on the Server9.7. Pattern Highlights
10. Infinite Data Pattern
10.1. Intent10.2. Motivation10.3. Applicability10.4. Associated Patterns10.5. Architecture10.6. Implementation10.6.1. Implementing the HTML Client10.6.2. Implementing the Task Manager10.7. Pattern Highlights
11. REST-Based Model View Controller Pattern
11.1. Intent11.2. Motivation11.3. Applicability11.4. Associated Patterns11.5. Architecture11.5.1. The Big Picture11.5.2. Defining an Appropriate Resource11.5.3. Defining the Calling Interface11.5.4. Defining the Data Format Foundation and the Extras11.6. Implementation11.6.1. Implementing a Search11.6.2. Creating a Search Engine Client Infrastructure11.6.3. Putting All of the Pieces Together11.7. Pattern Highlights

Content preview from Ajax Patterns and Best Practices

Chapter 8. Persistent Communications Pattern

Intent

The Persistent Communications pattern provides a mechanism enabling the client and the server to communicate with each other on a persistent basis so that the client can send messages to the server, and the server can send messages to the client.

Motivation

Client-server programming, which HTTP is, requires that the client call the server to process a request. The server obliges, processes the request, and sends a response. This is a standard run-of-the-mill operation.

Now imagine writing a web application that acts like a bulletin board. Each individual has the ability to create a message and post it. One extension would be offering the capability, when the messages are displayed, to indicate whether ...

Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.

Read now

Unlock full access

More than 5,000 organizations count on O’Reilly

O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.

Julian F.

Head of Cybersecurity

I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.

Addison B.

Field Engineer

I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.

Amir M.

Data Platform Tech Lead

I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.

Mark W.

Embedded Software Engineer

Publisher Resources

ISBN: 9781590596166Purchase book

Cloud Computing

Data Engineering

Data Science

AI & ML

Programming Languages

Software Architecture

IT/Ops

Security

Design