reklama - zainteresowany?

Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns - Helion

Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns
ebook
Autor: Michael Mahemoff
ISBN: 978-05-965-5361-6
stron: 656, Format: ebook
Data wydania: 2006-06-29
Księgarnia: Helion

Cena książki: 149,00 zł

Dodaj do koszyka Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns

Tagi: AJAX | Wzorce projektowe

Ajax, or Asynchronous JavaScript and XML, exploded onto the scene in the spring of 2005 and remains the hottest story among web developers. With its rich combination of technologies, Ajax provides astrong foundation for creating interactive web applications with XML or JSON-based web services by using JavaScript in the browser to process the web server response.

Ajax Design Patterns shows you best practices that can dramatically improve your web development projects. It investigates how others have successfully dealt with conflictingdesign principles in the past and then relays that information directly to you.

The patterns outlined in the book fall into four categories:

  • Foundational technology: Examines the raw technologies required for Ajax development
  • Programming: Exposes techniques that developers have discovered to ensure their Ajax applications are maintainable
  • Functionality and usability: Describes the types of user interfaces you'll come across in Ajax applications, as well as the new types of functionality that Ajax makes possible
  • Development: Explains the process being used to monitor, debug, and test Ajax applications

Ajax Design Patterns will also get you up to speed with core Ajax technologies, such as XMLHttpRequest, the DOM, and JSON. Technical discussions are followed by code examples so you can see for yourself just what is-and isn't-possible with Ajax. This handy reference will help you to produce high-quality Ajax architectures, streamline web application performance, and improve the userexperience.

Michael Mahemoff holds a PhD in Computer Science and Software Engineering from the University of Melbourne, where his thesis was "Design Reuse in Software Engineering and Human-Computer Interaction." He lives in London and consults on software development issues in banking, health care, and logistics.

"Michael Mahemoff's Ajax Design Patterns is a truly comprehensive compendium of webapplication design expertise, centered around but not limited to Ajax techniques. Polished nuggets of design wisdom are supported by tutorials and real-world code examples resulting in a book thatserves not only as an intermediate to expert handbook but also as an extensive reference for building rich interactive web applications."
--Brent Ashley, remote scripting pioneer

Dodaj do koszyka Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns

 

Osoby które kupowały "Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns", wybierały także:

  • ASP.NET MVC. Kompletny przewodnik dla programistów interaktywnych aplikacji internetowych w Visual Studio
  • Ajax. Implementacje
  • Ajax. Od podstaw
  • Ajax. Bezpieczne aplikacje internetowe
  • 80 sposobów na Ajax

Dodaj do koszyka Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns

Spis treści

Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns eBook -- spis treści

  • Ajax Design Patterns
    • SPECIAL OFFER: Upgrade this ebook with OReilly
    • A Note Regarding Supplemental Files
    • Preface
      • Who Should Read This Book?
      • Who Should Not Read This Book?
      • About the Examples
      • Browser Specifics
      • Organization of This Book
      • Conventions Used in This Book
      • Conventions in Code Examples
      • Safari Enabled
      • How to Contact Us
      • Acknowledgments
    • I. Introduction
      • 1. Introducing Ajax
        • 1.1. Ajax and the Usable Web
        • 1.2. The Rise of Ajax
        • 1.3. Ajaxifying the Web: The Story of Portals
        • 1.4. Webifying the Desktop: The Story of Office Applications
        • 1.5. Characteristics of Ajax Applications
          • 1.5.1. Applications, Not Just Web Sites
          • 1.5.2. Smooth, Continuous Interaction
          • 1.5.3. Live
          • 1.5.4. Supportive
          • 1.5.5. Visual Effects
          • 1.5.6. New Widgets
          • 1.5.7. New Styles of Interaction
          • 1.5.8. Standards-Based
        • 1.6. The Ajax Technologies
        • 1.7. Anatomy of a Server Call
        • 1.8. Ajax Trends
          • 1.8.1. Standards and Fragmentation
          • 1.8.2. Browser Adoption
          • 1.8.3. User Acceptance
          • 1.8.4. The Desktop
          • 1.8.5. Flash
          • 1.8.6. Rich Graphics
          • 1.8.7. The Two-Way Web
          • 1.8.8. Local Storage
          • 1.8.9. XForms
          • 1.8.10. JavaScript
          • 1.8.11. Development Support
          • 1.8.12. Hardware and Bandwidth Improvements
        • 1.9. Conclusions
      • 2. A Pattern-Led Tutorial
        • 2.1. Ajax Technologies in a Blink
          • 2.1.1. Preparing the Demos
          • 2.1.2. Display Manipulation and the DOM in a Blink
            • 2.1.2.1. Hello World!
            • 2.1.2.2. $( ) Convenience function
            • 2.1.2.3. Adding a link
          • 2.1.3. Web Remoting in a Blink
          • 2.1.4. Dynamic Behavior in a Blink
        • 2.2. Ajaxifying a Web App: One Pattern at a Time
          • 2.2.1. Background: Old-School Ajaxagram
          • 2.2.2. Step 1: Ajaxagram Done Ajax-Style
            • 2.2.2.1. Business logic: the anagram web service
            • 2.2.2.2. Presentation: initial HTML
            • 2.2.2.3. Application logic: JavaScript
          • 2.2.3. Step 2: Enhancing Functionality and Usability
            • 2.2.3.1. Live Search
            • 2.2.3.2. Progress Indicator
            • 2.2.3.3. One-Second Spotlight (Yellow Fade Technique)
          • 2.2.4. Step 3: Refactoring for Performance
          • 2.2.5. Step 4: Refactoring to an External Library
          • 2.2.6. Refactoring Exercises
            • 2.2.6.1. Foundational technology patterns
            • 2.2.6.2. Programming patterns
            • 2.2.6.3. Functionality and Usability patterns
            • 2.2.6.4. Development patterns
        • 2.3. Projects and Katas
        • 2.4. Conclusions
      • 3. Ajax Design: Principles and Patterns
        • 3.1. Desirable Attributes of Ajax Applications
        • 3.2. Designing for Ajax
          • 3.2.1. Usability Principles
          • 3.2.2. Software Design Principles
        • 3.3. Ajax Patterns Overview
        • 3.4. Anatomy of a Pattern
        • 3.5. Ajax Patterns Demos
        • 3.6. Conclusions
    • II. Foundational Technology Patterns
      • 4. Ajax App
        • 4.1. Ajax App
          • 4.1.1. Goal Story
          • 4.1.2. Problem
          • 4.1.3. Forces
          • 4.1.4. Solution
          • 4.1.5. Decisions
            • 4.1.5.1. Will your application be "Ajax Deluxe" or "Ajax Lite"?
            • 4.1.5.2. What browser requirements will there be to run your Ajax App?
            • 4.1.5.3. How will you treat browsers with insufficient technologies for Ajax?
            • 4.1.5.4. How much processing power will be required of the browser?
            • 4.1.5.5. How much networking capacity will be required?
          • 4.1.6. Real-World Examples
          • 4.1.7. Code Example
          • 4.1.8. Alternatives
            • 4.1.8.1. Conventional web app
            • 4.1.8.2. Flash app
            • 4.1.8.3. Java applets
            • 4.1.8.4. Desktop app
            • 4.1.8.5. Mobile app
          • 4.1.9. Related Patterns
      • 5. Display Manipulation
        • 5.1. Display Morphing
          • 5.1.1. Goal Story
          • 5.1.2. Problem
          • 5.1.3. Forces
          • 5.1.4. Solution
          • 5.1.5. Decisions
            • 5.1.5.1. Will you alter the display via classname or style?
            • 5.1.5.2. What sort of properties will be used?
          • 5.1.6. Real-World Examples
            • 5.1.6.1. Ajax-S
            • 5.1.6.2. Digg Spy
            • 5.1.6.3. Ajax Spell Checker
          • 5.1.7. Code Example: AjaxPatterns Countdown Demo
          • 5.1.8. Related Patterns
            • 5.1.8.1. Page Rearrangement
          • 5.1.9. Metaphor
          • 5.1.10. Want To Know More?
        • 5.2. Page Rearrangement
          • 5.2.1. Goal Story
          • 5.2.2. Problem
          • 5.2.3. Forces
          • 5.2.4. Solution
          • 5.2.5. Decisions
            • 5.2.5.1. Which positioning style to use?
            • 5.2.5.2. How will you protect against memory leaks?
          • 5.2.6. Real-World Examples
            • 5.2.6.1. TadaList
            • 5.2.6.2. Super Maryo World
            • 5.2.6.3. Kiko
          • 5.2.7. Code Example: AjaxPatterns Basic Wiki
          • 5.2.8. Related Patterns
            • 5.2.8.1. Display Morphing
          • 5.2.9. Metaphor
      • 6. Web Remoting
        • 6.1. Web Service
          • 6.1.1. Goal Story
          • 6.1.2. Problem
          • 6.1.3. Forces
          • 6.1.4. Solution
          • 6.1.5. Decisions
            • 6.1.5.1. How will the web service be used?
            • 6.1.5.2. How will you prevent third-party usage?
          • 6.1.6. Real-World Examples
            • 6.1.6.1. Technorati API
            • 6.1.6.2. NetVibes
            • 6.1.6.3. Wish-O-Matic
          • 6.1.7. Code Example: AjaxPatterns testAjaxCaller
          • 6.1.8. Related Patterns
            • 6.1.8.1. Web Services patterns
            • 6.1.8.2. Web Remoting patterns
            • 6.1.8.3. Cross-Domain Proxy
            • 6.1.8.4. Simulation Service
            • 6.1.8.5. Service Test
        • 6.2. XMLHttpRequest Call
          • 6.2.1. Goal Story
          • 6.2.2. Problem
          • 6.2.3. Forces
          • 6.2.4. Solution
            • 6.2.4.1. Creating XMLHttpRequest objects
            • 6.2.4.2. Asynchronous calls
            • 6.2.4.3. Detecting errors
            • 6.2.4.4. Handling POSTs and other request types
            • 6.2.4.5. Constraints on external domains
            • 6.2.4.6. XML responses
            • 6.2.4.7. The XMLHttpRequest API: a summary
          • 6.2.5. Decisions
            • 6.2.5.1. What kind of content will web services provide?
            • 6.2.5.2. How will caching be controlled?
            • 6.2.5.3. How will you deal with errors?
          • 6.2.6. Real-World Examples
            • 6.2.6.1. Lace Chat
            • 6.2.6.2. Backbase
            • 6.2.6.3. Anyterm
            • 6.2.6.4. Mint
          • 6.2.7. Code Example: AjaxPatterns TestAjaxCaller
          • 6.2.8. Alternatives
            • 6.2.8.1. Page refreshes
            • 6.2.8.2. IFrame Call
            • 6.2.8.3. HTTP Streaming
            • 6.2.8.4. Richer Plugin
            • 6.2.8.5. On-Demand JavaScript
            • 6.2.8.6. Image-Cookie Call
            • 6.2.8.7. Stylesheet Call
            • 6.2.8.8. 204 Response
            • 6.2.8.9. Import XML Document
          • 6.2.9. Metaphor
        • 6.3. IFrame Call
          • 6.3.1. Goal Story
          • 6.3.2. Problem
          • 6.3.3. Forces
          • 6.3.4. Solution
          • 6.3.5. Real-World Examples
            • 6.3.5.1. Google Maps
            • 6.3.5.2. Scoop framework, Kuro5hin
            • 6.3.5.3. PXL8 Demo
            • 6.3.5.4. HTMLHttpRequest Library
          • 6.3.6. Code Refactoring: AjaxPatterns Sum Demo
          • 6.3.7. Alternatives
            • 6.3.7.1. XMLHttpRequest Call
            • 6.3.7.2. Frame Call
          • 6.3.8. Metaphor
        • 6.4. HTTP Streaming
          • 6.4.1. Goal Story
          • 6.4.2. Problem
          • 6.4.3. Forces
          • 6.4.4. Solution
          • 6.4.5. Decisions
            • 6.4.5.1. How long will you keep the connection open?
            • 6.4.5.2. How will you decide when to close the connection?
            • 6.4.5.3. How will the browser distinguish between messages?
          • 6.4.6. Real-World Examples
            • 6.4.6.1. LivePage
            • 6.4.6.2. Jotspot Live
            • 6.4.6.3. Realtime on Rails
            • 6.4.6.4. Lightstreamer engine
            • 6.4.6.5. Pushlets framework
          • 6.4.7. Code Refactoring: AjaxPatterns Streaming Wiki
          • 6.4.8. Alternatives
            • 6.4.8.1. Periodic Refresh
            • 6.4.8.2. TCP connection
          • 6.4.9. Related Patterns
            • 6.4.9.1. Distributed Events
          • 6.4.10. Metaphor
          • 6.4.11. Want To Know More?
          • 6.4.12. Acknowledgments
        • 6.5. On-Demand JavaScript
          • 6.5.1. Goal Story
          • 6.5.2. Problem
          • 6.5.3. Forces
          • 6.5.4. Solution
          • 6.5.5. Decisions
            • 6.5.5.1. Will you use Service Eval or Script Tag Creation?
            • 6.5.5.2. With Lazy Loading, how will you break modules down?
            • 6.5.5.3. With Lazy Loading, at what stage will the script download the JavaScript?
          • 6.5.6. Real-World Examples
            • 6.5.6.1. MapBuilder
            • 6.5.6.2. Delicious/Yahoo! APIs
            • 6.5.6.3. Dojo packaging framework
            • 6.5.6.4. JSAN import system
          • 6.5.7. Code Example, AjaxPatterns On-Demand JavaScript Wiki
            • 6.5.7.1. Introducing On-Demand JavaScript to the Wiki Demo
            • 6.5.7.2. Separate JavaScript: Extracting upload.js
            • 6.5.7.3. Script Tag Creation On-Demand JavaScript
            • 6.5.7.4. Service Eval On-Demand JavaScript
          • 6.5.8. Related Patterns
            • 6.5.8.1. HTML Message
            • 6.5.8.2. Predictive Fetch
            • 6.5.8.3. Multi-Stage Download
          • 6.5.9. Want to Know More?
      • 7. Dynamic Behavior
        • 7.1. User Action
          • 7.1.1. Goal Story
          • 7.1.2. Problem
          • 7.1.3. Forces
          • 7.1.4. Solution
          • 7.1.5. Decisions
            • 7.1.5.1. What events will the script listen for?
            • 7.1.5.2. What attributes of the event will be inspected?
            • 7.1.5.3. Will event handlers be registered after the page has loaded?
          • 7.1.6. Real-World Examples
            • 7.1.6.1. Google Reader
            • 7.1.6.2. Google Maps
            • 7.1.6.3. Backpack
          • 7.1.7. Code Example: Basic AjaxPatterns Demos
          • 7.1.8. Alternatives
            • 7.1.8.1. "Click n' Wait"
            • 7.1.8.2. Richer forms
          • 7.1.9. Related Patterns
            • 7.1.9.1. Display Morphing, Page Rearrangement
            • 7.1.9.2. XMLHttpRequest Call, IFrame Call
        • 7.2. Scheduling
          • 7.2.1. Goal Story
          • 7.2.2. Problem
          • 7.2.3. Forces
          • 7.2.4. Solution
          • 7.2.5. Real-World Examples
            • 7.2.5.1. Claude Hussenet's Portal
            • 7.2.5.2. Google Suggest
            • 7.2.5.3. Apple iTunes counter
            • 7.2.5.4. Backpack
          • 7.2.6. Code Example: AjaxPatterns Basic Wiki
          • 7.2.7. Alternatives
            • 7.2.7.1. HTTP Meta Refresh
          • 7.2.8. Metaphor
      • 8. Extended Technologies
        • 8.1. Richer Plugin
          • 8.1.1. Goal Story
          • 8.1.2. Problem
          • 8.1.3. Forces
          • 8.1.4. Solution
          • 8.1.5. Decisions
            • 8.1.5.1. Will you reuse a third-party plugin or develop your own?
            • 8.1.5.2. What will happen if the plugin's not installed?
          • 8.1.6. Real-World Examples
            • 8.1.6.1. Amazon Mini Shop
            • 8.1.6.2. Google Toolbar and Google Suggest for Firefox
            • 8.1.6.3. Odeo
            • 8.1.6.4. TiddlyWiki
          • 8.1.7. Code Example: Amazon Mini Shop
          • 8.1.8. Alternatives
            • 8.1.8.1. Desktop Client
          • 8.1.9. Related Patterns
            • 8.1.9.1. Fat Client
            • 8.1.9.2. Single Page Application
            • 8.1.9.3. Bookmarklet
            • 8.1.9.4. Browser-Side Cache
          • 8.1.10. Metaphor
          • 8.1.11. Want to Know More?
    • III. Programming Patterns
      • 9. Web Services
        • 9.1. RESTful Service
          • 9.1.1. Developer Story
          • 9.1.2. Problem
          • 9.1.3. Forces
          • 9.1.4. Solution
            • 9.1.4.1. Motivating REST: many ways to skin a call
            • 9.1.4.2. Introduction to RESTful principles
          • 9.1.5. RESTful principles
            • 9.1.5.1. URLs reflect resources
            • 9.1.5.2. HTTP methods reflect actions
            • 9.1.5.3. GET for queries, and only for queries
            • 9.1.5.4. Services should be stateless
            • 9.1.5.5. Services should be idempotent
            • 9.1.5.6. Services use hyperlinks
            • 9.1.5.7. Services documents themselves
            • 9.1.5.8. Services constrain data formats
            • 9.1.5.9. Handling arbitrary transactions
            • 9.1.5.10. Weighing Up REST
          • 9.1.6. Real-World Examples
            • 9.1.6.1. Blogger API
          • 9.1.7. Code Example: AjaxPatterns RESTful Shop Demo
            • 9.1.7.1. Reading categories list
            • 9.1.7.2. Reading an individual category
            • 9.1.7.3. Reading cart contents
            • 9.1.7.4. Changing cart contents
          • 9.1.8. Alternatives
            • 9.1.8.1. RPC Service
          • 9.1.9. Related Patterns
            • 9.1.9.1. XML Message
            • 9.1.9.2. XML Data Island
            • 9.1.9.3. Unique URLs
          • 9.1.10. Metaphor
          • 9.1.11. Want To Know More?
          • 9.1.12. Acknowledgments
        • 9.2. RPC Service
          • 9.2.1. Developer Story
          • 9.2.2. Problem
          • 9.2.3. Forces
          • 9.2.4. Solution
          • 9.2.5. Real-World Examples
            • 9.2.5.1. Kiko
            • 9.2.5.2. Flickr API
          • 9.2.6. Code Example: AjaxPatterns RPC Shop Demo
            • 9.2.6.1. Reading the Categories list
            • 9.2.6.2. Reading an individual category
            • 9.2.6.3. Reading cart contents
            • 9.2.6.4. Changing cart contents
          • 9.2.7. Alternatives
            • 9.2.7.1. RESTful Service
          • 9.2.8. Related Patterns
            • 9.2.8.1. Ajax Stub
            • 9.2.8.2. Plain-Text Message, XML Message
          • 9.2.9. Metaphor
        • 9.3. Ajax Stub
          • 9.3.1. Developer Story
          • 9.3.2. Problem
          • 9.3.3. Forces
          • 9.3.4. Solution
          • 9.3.5. Decisions
            • 9.3.5.1. How will you secure the server-side function?
          • 9.3.6. Real-World Examples
            • 9.3.6.1. SAJAX framework
            • 9.3.6.2. DWR framework
            • 9.3.6.3. CL-AJAX framework
          • 9.3.7. Code Refactoring: AjaxPatterns SAJAX Sum
          • 9.3.8. Alternatives
            • 9.3.8.1. XMLHttpRequest Call
            • 9.3.8.2. XML-RPC and SOAP
          • 9.3.9. Related Patterns
            • 9.3.9.1. RPC Service
            • 9.3.9.2. JSON Message
        • 9.4. HTML Message
          • 9.4.1. Developer Story
          • 9.4.2. Problem
          • 9.4.3. Forces
          • 9.4.4. Solution
          • 9.4.5. Decisions
            • 9.4.5.1. At what level of granularity will the HTML apply?
            • 9.4.5.2. How much style will be contained in the message?
          • 9.4.6. Real-World Examples
            • 9.4.6.1. Digg Spy
            • 9.4.6.2. Rapha
            • 9.4.6.3. Amazon Zuggest
            • 9.4.6.4. TalkDigger
          • 9.4.7. Code Example: Digg Spy
          • 9.4.8. Alternatives
            • 9.4.8.1. Plain-Text Message, XML Message, JSON Message
          • 9.4.9. Related Patterns
            • 9.4.9.1. On-Demand JavaScript
          • 9.4.10. Metaphor
        • 9.5. Plain-Text Message
          • 9.5.1. Developer Story
          • 9.5.2. Problem
          • 9.5.3. Forces
          • 9.5.4. Solution
          • 9.5.5. Real-World Examples
            • 9.5.5.1. Lace Chat
            • 9.5.5.2. Magnetic Poetry
            • 9.5.5.3. HousingMaps
          • 9.5.6. Code Example: Lace Chat
          • 9.5.7. Alternatives
            • 9.5.7.1. XML Message
        • 9.6. XML Message
          • 9.6.1. Devloper Story
          • 9.6.2. Problem
          • 9.6.3. Forces
          • 9.6.4. Solution
          • 9.6.5. Decisions
            • 9.6.5.1. How will the server generate XML?
            • 9.6.5.2. Will you specify a DTD or Schema?
            • 9.6.5.3. When the browser needs to render the message, how it will transform the XML?
          • 9.6.6. Real-World Examples
            • 9.6.6.1. Netflix Top 100
            • 9.6.6.2. Protopage
            • 9.6.6.3. Google Maps
          • 9.6.7. Code Refactoring: AjaxPatterns XML Sum
          • 9.6.8. Alternatives
            • 9.6.8.1. Plain-Text Message
            • 9.6.8.2. JSON Message
        • 9.7. JSON Message
          • 9.7.1. Developer Story
          • 9.7.2. Problem
          • 9.7.3. Forces
          • 9.7.4. Solution
          • 9.7.5. Real-World Examples
            • 9.7.5.1. Kiko
            • 9.7.5.2. Delicious JSON Feed
            • 9.7.5.3. Route Planning
            • 9.7.5.4. Ajax.Net framework
          • 9.7.6. Code Example: Kiko
          • 9.7.7. Alternatives
            • 9.7.7.1. XML Message
          • 9.7.8. Related Patterns
            • 9.7.8.1. Ajax Stub
            • 9.7.8.2. On-Demand JavaScript
      • 10. Browser-Server Dialogue
        • 10.1. Call Tracking
          • 10.1.1. Developer Story
          • 10.1.2. Problem
          • 10.1.3. Forces
          • 10.1.4. Solution
          • 10.1.5. Real-World Examples
            • 10.1.5.1. Ajax Client Engine (ACE) library
            • 10.1.5.2. AjaxCaller library
            • 10.1.5.3. libXmlRequest library
          • 10.1.6. Code Example: Ajax Client Engine (ACE)
          • 10.1.7. Alternatives
            • 10.1.7.1. Fire-and-forget
            • 10.1.7.2. Global XMLHttpRequest
          • 10.1.8. Metaphor
          • 10.1.9. Acknowledgments
        • 10.2. Periodic Refresh
          • 10.2.1. Developer Story
          • 10.2.2. Problem
          • 10.2.3. Forces
          • 10.2.4. Solution
          • 10.2.5. Decisions
            • 10.2.5.1. How long will the refresh period be?
          • 10.2.6. Real-World Examples
            • 10.2.6.1. Lace Chat
            • 10.2.6.2. Magnetic Poetry
            • 10.2.6.3. Claude Hussenet's portal
          • 10.2.7. Code Examples
            • 10.2.7.1. Lace
          • 10.2.8. Code Refactoring: AjaxPatterns Periodic Time
          • 10.2.9. Alternatives
            • 10.2.9.1. HTTP Streaming
          • 10.2.10. Related Patterns
            • 10.2.10.1. Distributed Events
            • 10.2.10.2. Fat Client, Browser-Side Cache, Guesstimate
            • 10.2.10.3. Submission Throttling
            • 10.2.10.4. Heartbeat
          • 10.2.11. Metaphor
        • 10.3. Submission Throttling
          • 10.3.1. Developer Story
          • 10.3.2. Problem
          • 10.3.3. Forces
          • 10.3.4. Solution
          • 10.3.5. Decisions
            • 10.3.5.1. How will the server deal with incoming commands? Will all commands still be valid?
            • 10.3.5.2. How will buffer uploads be triggered?
            • 10.3.5.3. How many buffers per browser application?
            • 10.3.5.4. How long should the throttle period be?
          • 10.3.6. Real-World Examples
            • 10.3.6.1. Google Suggest
            • 10.3.6.2. Zuggest
            • 10.3.6.3. Gmail
            • 10.3.6.4. Prototype framework
          • 10.3.7. Code Example: AjaxPatterns Assistive Search
          • 10.3.8. Related Patterns
            • 10.3.8.1. Periodic Refresh
            • 10.3.8.2. Progress Indicator
          • 10.3.9. Metaphor
        • 10.4. Explicit Submission
          • 10.4.1. Developer Story
          • 10.4.2. Problem
          • 10.4.3. Forces
          • 10.4.4. Solution
          • 10.4.5. Decisions
            • 10.4.5.1. How will the user request the submission?
            • 10.4.5.2. How will you deal with frequent submissions?
          • 10.4.6. Real-World Examples
            • 10.4.6.1. Lace Chat
            • 10.4.6.2. The Fonz
            • 10.4.6.3. A9
          • 10.4.7. Code Refactoring: AjaxPatterns Form-Based Sum
          • 10.4.8. Alternatives
            • 10.4.8.1. Submission Throttling
          • 10.4.9. Related Patterns
            • 10.4.9.1. Live Form
            • 10.4.9.2. Progress Indicator
          • 10.4.10. Metaphor
        • 10.5. Distributed Events
          • 10.5.1. Developer Story
          • 10.5.2. Problem
          • 10.5.3. Forces
          • 10.5.4. Solution
          • 10.5.5. Decisions about Distributed Events
            • 10.5.5.1. Will you publish a history or just the current state?
            • 10.5.5.2. For observer-style events, will you propagate the details of what's changed, or just point to the object that's changed?
            • 10.5.5.3. What information will accompany the event notification?
            • 10.5.5.4. Will events be processed synchronously or asynchronously?
          • 10.5.6. Real-World Examples
            • 10.5.6.1. ActiveMQ Servlet Adaptor
            • 10.5.6.2. MapBuilder
            • 10.5.6.3. Dojo Events Library
            • 10.5.6.4. LivePage Library
          • 10.5.7. Code Refactoring: AjaxPatterns Distributed Events Wiki Demo
            • 10.5.7.1. Refactoring to an event mechanism
            • 10.5.7.2. Introducing a watchlist
          • 10.5.8. Related Patterns
            • 10.5.8.1. Periodic Refresh, HTTP Streaming
            • 10.5.8.2. RESTful Service
            • 10.5.8.3. XML Data Island
          • 10.5.9. Metaphor
        • 10.6. Cross-Domain Proxy
          • 10.6.1. Developer Story
          • 10.6.2. Problem
          • 10.6.3. Forces
          • 10.6.4. Solution
          • 10.6.5. Decisions
            • 10.6.5.1. What external content will be accessed?
            • 10.6.5.2. How will you connect to the external server?
            • 10.6.5.3. How will you deal with errors and delays in accessing the service?
            • 10.6.5.4. Under what licensing terms will you access the remote service?
          • 10.6.6. Real-World Examples
            • 10.6.6.1. WPLicense
            • 10.6.6.2. Housing Maps (Craigslist and Google Maps)
            • 10.6.6.3. Bill Gates Wealth Clock
            • 10.6.6.4. CPaint library
          • 10.6.7. Code Example: WPLicense
            • 10.6.7.1. 1. Retrieving license types
            • 10.6.7.2. 2. Retrieving license questions
            • 10.6.7.3. 3. Handling user answers
          • 10.6.8. Alternatives
            • 10.6.8.1. On-Demand JavaScript
            • 10.6.8.2. Shared document.domain
            • 10.6.8.3. Images
          • 10.6.9. Related Patterns
            • 10.6.9.1. Performance Optimization patterns
          • 10.6.10. Want to Know More?
      • 11. DOM Population
        • 11.1. XML Data Island
          • 11.1.1. Developer Story
          • 11.1.2. Problem
          • 11.1.3. Forces
          • 11.1.4. Solution
          • 11.1.5. Real-World Examples
            • 11.1.5.1. PerfectXML Demo
            • 11.1.5.2. Mozilla.org demo
            • 11.1.5.3. TechRepublic demo
          • 11.1.6. Code Refactoring: AjaxPatterns XML Data Island Sum
          • 11.1.7. Alternatives
            • 11.1.7.1. Browser-Side XSLT
            • 11.1.7.2. Browser-Side Templating
            • 11.1.7.3. Browser-Side Cache
          • 11.1.8. Metaphor
        • 11.2. Browser-Side XSLT
          • 11.2.1. Developer Story
          • 11.2.2. Problem
          • 11.2.3. Forces
          • 11.2.4. Solution
          • 11.2.5. Decisions
            • 11.2.5.1. How will you obtain the XSLT stylesheet?
          • 11.2.6. Real-World Examples
            • 11.2.6.1. Google Maps
            • 11.2.6.2. Kupu
            • 11.2.6.3. AJAX-S
            • 11.2.6.4. Sarissa framework
          • 11.2.7. Code Refactoring: AjaxPatterns XSLT Drilldown Demo
          • 11.2.8. Alternatives
            • 11.2.8.1. Browser-Side Templating
          • 11.2.9. Related Patterns
            • 11.2.9.1. XML Message
            • 11.2.9.2. XML Data Island
          • 11.2.10. Metaphor
        • 11.3. Browser-Side Templating
          • 11.3.1. Developer Story
          • 11.3.2. Problem
          • 11.3.3. Forces
          • 11.3.4. Solution
          • 11.3.5. Decisions
            • 11.3.5.1. How will you obtain the template?
            • 11.3.5.2. Will the template include any code? How much?
            • 11.3.5.3. How to prepare the template's context?
          • 11.3.6. Real-World Examples
            • 11.3.6.1. Ajax Pages framework
            • 11.3.6.2. JavaScript Templates framework
            • 11.3.6.3. Backbase framework
          • 11.3.7. Code Refactoring: AjaxPatterns Templating Drilldown Demo
            • 11.3.7.1. Initial version
            • 11.3.7.2. Refactored to render from a template
            • 11.3.7.3. Refactored to improve template context
          • 11.3.8. Alternatives
            • 11.3.8.1. Browser-Side XSLT
          • 11.3.9. Related Patterns
            • 11.3.9.1. XML Message
            • 11.3.9.2. JSON Message
          • 11.3.10. Metaphor
      • 12. Code Generation and Reuse
        • 12.1. Server-Side Code Generation
          • 12.1.1. Developer Story
          • 12.1.2. Problem
          • 12.1.3. Forces
          • 12.1.4. Solution
          • 12.1.5. Real-World Examples
            • 12.1.5.1. Echo2
            • 12.1.5.2. Ruby On Rails framework
            • 12.1.5.3. Backbase
            • 12.1.5.4. AjaxTags library
            • 12.1.5.5. Comfort.ASP library
          • 12.1.6. Code Example: Echo2 Number Guess
          • 12.1.7. Alternatives
            • 12.1.7.1. Browser-Side Templating
          • 12.1.8. Related Patterns
            • 12.1.8.1. HTML Message
        • 12.2. Cross-Browser Component
          • 12.2.1. Developer Story
          • 12.2.2. Problem
          • 12.2.3. Forces
          • 12.2.4. Solution
          • 12.2.5. Decisions
            • 12.2.5.1. What browser-specific criteria is used to create the Cross-Browser Component?
            • 12.2.5.2. What if a feature isn't supported by the current browser?
          • 12.2.6. Real-World Examples
            • 12.2.6.1. HTMLHttpRequest library
          • 12.2.7. Code Example: HTMLHttpRequest Library
          • 12.2.8. Related Patterns
            • 12.2.8.1. Server-Side Code Generation
            • 12.2.8.2. On-Demand JavaScript
          • 12.2.9. Metaphor
          • 12.2.10. Want to Know More?
      • 13. Performance Optimization
        • 13.1. Browser-Side Cache
          • 13.1.1. Developer Story
          • 13.1.2. Problem
          • 13.1.3. Forces
          • 13.1.4. Solution
          • 13.1.5. Decisions
            • 13.1.5.1. What will be stored as keys? For values?
            • 13.1.5.2. How will cache size be kept under control?
            • 13.1.5.3. How will you protect against stale data?
          • 13.1.6. Real-World Examples
            • 13.1.6.1. libXmlRequest library
          • 13.1.7. Code Example: Cached Sum Demo
            • 13.1.7.1. Including the query in the response
            • 13.1.7.2. An infinite cache
            • 13.1.7.3. A finite cache
          • 13.1.8. Alternatives
            • 13.1.8.1. Built-in browser cache
            • 13.1.8.2. Server-side cache
          • 13.1.9. Related Patterns
            • 13.1.9.1. Submission Throttling
        • 13.2. Predictive Fetch
          • 13.2.1. Developer Story
          • 13.2.2. Problem
          • 13.2.3. Forces
          • 13.2.4. Solution
          • 13.2.5. Decisions
            • 13.2.5.1. How much information will be pre-fetched?
            • 13.2.5.2. Will it be the server or the browser that anticipates user actions?
            • 13.2.5.3. What information can be used to anticipate user actions?
          • 13.2.6. Real-World Examples
            • 13.2.6.1. Google Maps
            • 13.2.6.2. map.search.ch
            • 13.2.6.3. Firefox "Prefetch"
            • 13.2.6.4. International Herald Tribune
          • 13.2.7. Code Refactoring: AjaxPatterns Predictive Fetch Sum
          • 13.2.8. Alternatives
            • 13.2.8.1. Fat Client
            • 13.2.8.2. Server priming
          • 13.2.9. Related Patterns
            • 13.2.9.1. Guesstimate
            • 13.2.9.2. Browser-Side Cache
          • 13.2.10. Metaphor
        • 13.3. Guesstimate
          • 13.3.1. Developer Story
          • 13.3.2. Problem
          • 13.3.3. Forces
          • 13.3.4. Solution
          • 13.3.5. Decisions
            • 13.3.5.1. How often will real data be fetched? How often will Guesstimates be made?
            • 13.3.5.2. How will the Guesstimate be consolidated with real data?
            • 13.3.5.3. Will users be aware a Guesstimate is taking place?
            • 13.3.5.4. What support will the server provide?
          • 13.3.6. Real-World Examples
            • 13.3.6.1. Apple iTunes counter
            • 13.3.6.2. Gmail Storage Space
          • 13.3.7. Code Example: iTunes Counter
          • 13.3.8. Related Patterns
            • 13.3.8.1. Periodic Refresh
            • 13.3.8.2. Predictive Fetch
            • 13.3.8.3. Fat Client
          • 13.3.9. Metaphor
        • 13.4. Multi-Stage Download
          • 13.4.1. Developer Story
          • 13.4.2. Problem
          • 13.4.3. Forces
          • 13.4.4. Solution
          • 13.4.5. Decisions
            • 13.4.5.1. How will the page be divided into blocks?
            • 13.4.5.2. How will the page be structured?
            • 13.4.5.3. What happens to the blocks while their content is being downloaded?
            • 13.4.5.4. Will the calls be issued simultaneously?
          • 13.4.6. Real-World Examples
            • 13.4.6.1. Kayak
            • 13.4.6.2. NetVibes
            • 13.4.6.3. TalkDigger
          • 13.4.7. Code Example: AjaxPatterns Portal
          • 13.4.8. Alternatives
            • 13.4.8.1. All-In-One
          • 13.4.9. Related Patterns
            • 13.4.9.1. Portlet
            • 13.4.9.2. Guesstimate
            • 13.4.9.3. Progress Indicator
            • 13.4.9.4. On-Demand JavaScript
          • 13.4.10. Metaphor
        • 13.5. Fat Client
          • 13.5.1. Developer Story
          • 13.5.2. Problem
          • 13.5.3. Forces
          • 13.5.4. Solution
          • 13.5.5. Decisions
            • 13.5.5.1. How will business and application logic be implemented in the browser?
          • 13.5.6. Real-World Examples
            • 13.5.6.1. NumSum
            • 13.5.6.2. Gmail
            • 13.5.6.3. DHTML Lemmings
            • 13.5.6.4. JS/UIX shell
          • 13.5.7. Code Example: AjaxPatterns Basic Wiki
          • 13.5.8. Alternatives
            • 13.5.8.1. Thin client
            • 13.5.8.2. Desktop client
          • 13.5.9. Related Patterns
            • 13.5.9.1. Periodic Refresh
            • 13.5.9.2. Submission Throttling
            • 13.5.9.3. Widgets
            • 13.5.9.4. On-Demand JavaScript
            • 13.5.9.5. Drag-And-Drop
            • 13.5.9.6. Host-Proof Hosting
          • 13.5.10. Metaphor
          • 13.5.11. Want to Know More?
    • IV. Functionality and Usability Patterns
      • 14. Widgets
        • 14.1. Slider
          • 14.1.1. Goal Story
          • 14.1.2. Problem
          • 14.1.3. Forces
          • 14.1.4. Solution
          • 14.1.5. Decisions
            • 14.1.5.1. How will you orient the Slider?
            • 14.1.5.2. What scale will you use?
            • 14.1.5.3. How will you present the scale?
          • 14.1.6. Real-World Examples
            • 14.1.6.1. Yahoo! Mindset
            • 14.1.6.2. Amazon Diamond Search
            • 14.1.6.3. Google Maps
            • 14.1.6.4. Katrina-Boston map overlay
            • 14.1.6.5. WebFX Slider Demo
          • 14.1.7. Code Example: Yahoo! Mindset
          • 14.1.8. Alternatives
            • 14.1.8.1. Conventional controls: radiobuttons and selector field
          • 14.1.9. Related Patterns
            • 14.1.9.1. Drag-And-Drop
          • 14.1.10. Metaphor
        • 14.2. Progress Indicator
          • 14.2.1. Goal Story
          • 14.2.2. Problem
          • 14.2.3. Forces
          • 14.2.4. Solution
          • 14.2.5. Decisions
            • 14.2.5.1. What sort of Progress Indicator will you use?
            • 14.2.5.2. How will you provide feedback during longer delays?
          • 14.2.6. Real-World Examples
            • 14.2.6.1. Amazon Diamond Search
            • 14.2.6.2. Amazon Zuggest
            • 14.2.6.3. Protopage
            • 14.2.6.4. TalkDigger
            • 14.2.6.5. Kayak
            • 14.2.6.6. The Pick'em Game
          • 14.2.7. Code Refactoring: AjaxPatterns Progress Indicator Demo
          • 14.2.8. Related Patterns
            • 14.2.8.1. Status Area
            • 14.2.8.2. Popup
            • 14.2.8.3. One-Second Spotlight
            • 14.2.8.4. Guesstimate
            • 14.2.8.5. Distributed Events
          • 14.2.9. Metaphor
          • 14.2.10. Want to Know More?
        • 14.3. Drilldown
          • 14.3.1. Goal Story
          • 14.3.2. Problem
          • 14.3.3. Forces
          • 14.3.4. Solution
          • 14.3.5. Decisions
            • 14.3.5.1. Will you call on the server each time the user navigates through the Drilldown?
          • 14.3.6. Real-World Examples
            • 14.3.6.1. Betfair
            • 14.3.6.2. Backbase portal
            • 14.3.6.3. OpenRico accordian widget
          • 14.3.7. Code Refactoring: AjaxPatterns Drilldown Portal
            • 14.3.7.1. Overview
            • 14.3.7.2. Browser-side implementation
            • 14.3.7.3. Server-Side Implementation
            • 14.3.7.4. Further refactoring: a Drilldown with dynamic content
          • 14.3.8. Alternatives
            • 14.3.8.1. Live Search
            • 14.3.8.2. Tree
          • 14.3.9. Related Patterns
            • 14.3.9.1. Microlink
            • 14.3.9.2. Browser-Side Cache
            • 14.3.9.3. Portlet
        • 14.4. Data Grid
          • 14.4.1. Goal Story
          • 14.4.2. Problem
          • 14.4.3. Forces
          • 14.4.4. Solution
          • 14.4.5. Decisions
            • 14.4.5.1. Will the Grid be Read-Only or Mutable?
          • 14.4.6. Real-World Examples
            • 14.4.6.1. OpenRico Data Grid example
            • 14.4.6.2. NumSum
            • 14.4.6.3. Oddpost
            • 14.4.6.4. Delta Vacations
          • 14.4.7. Code Example: OpenRico Data Grid
          • 14.4.8. Related Patterns
            • 14.4.8.1. Virtual Workspace
            • 14.4.8.2. Browser-Side Cache
            • 14.4.8.3. Predictive Fetch
            • 14.4.8.4. Progress Indicator
          • 14.4.9. Metaphor
          • 14.4.10. Acknowledgments
        • 14.5. Rich Text Editor
          • 14.5.1. Goal Story
          • 14.5.2. Problem
          • 14.5.3. Forces
          • 14.5.4. Solution
          • 14.5.5. Real-World Examples
            • 14.5.5.1. FCKEditor library
            • 14.5.5.2. Jotspot, Dojo Rich Text Editor
            • 14.5.5.3. Writely
            • 14.5.5.4. Wikipedia
            • 14.5.5.5. Rich Text Editor
          • 14.5.6. Code Example: FCKEditor
          • 14.5.7. Related Patterns
            • 14.5.7.1. Virtual Workspace
            • 14.5.7.2. Progress Indicator
            • 14.5.7.3. Status Area
          • 14.5.8. Metaphor
        • 14.6. Suggestion
          • 14.6.1. Goal Story
          • 14.6.2. Problem
          • 14.6.3. Forces
          • 14.6.4. Solution
          • 14.6.5. Decisions
            • 14.6.5.1. What algorithm will be used to produce the Suggestions?
            • 14.6.5.2. How will the Suggestions be ordered?
            • 14.6.5.3. How many Suggestions will be shown?
            • 14.6.5.4. What auxiliary information will be present with each Suggestion?
          • 14.6.6. Real-World Examples
            • 14.6.6.1. Kayak
            • 14.6.6.2. Google Suggest
            • 14.6.6.3. Delicious, Amazon
          • 14.6.7. Code Example: Kayak
          • 14.6.8. Alternatives
            • 14.6.8.1. Selector
          • 14.6.9. Related Patterns
            • 14.6.9.1. Browser-Side Cache
            • 14.6.9.2. Guesstimate
            • 14.6.9.3. Predictive Fetch
            • 14.6.9.4. Submission Throttling
            • 14.6.9.5. Highlight
            • 14.6.9.6. Lazy Registration
            • 14.6.9.7. Live Search
          • 14.6.10. Want to Know More?
          • 14.6.11. Acknowledgments
        • 14.7. Live Search
          • 14.7.1. Goal Story
          • 14.7.2. Problem
          • 14.7.3. Forces
          • 14.7.4. Solution
          • 14.7.5. Decisions
            • 14.7.5.1. How will you interpret incomplete text?
            • 14.7.5.2. How verbose will the results be?
            • 14.7.5.3. What will happen when there are too many results?
          • 14.7.6. Real-World Examples
            • 14.7.6.1. Delta Vacations
            • 14.7.6.2. ListSomething.com
            • 14.7.6.3. Amazon Diamond Search
            • 14.7.6.4. Skype
          • 14.7.7. Code Example: Delta Vacations
            • 14.7.7.1. Delta Vacations
            • 14.7.7.2. Assistive Search demo
          • 14.7.8. Related Patterns
            • 14.7.8.1. Progress Indicator
            • 14.7.8.2. Data Grid
            • 14.7.8.3. Virtual Workspace
            • 14.7.8.4. One-Second Spotlight
            • 14.7.8.5. Submission Throttling
            • 14.7.8.6. Unique URLs
            • 14.7.8.7. Predictive Fetch
            • 14.7.8.8. Suggestion
        • 14.8. Live Command-Line
          • 14.8.1. Goal Story
          • 14.8.2. Problem
          • 14.8.3. Forces
          • 14.8.4. Solution
          • 14.8.5. Decisions
            • 14.8.5.1. Where will the partial command be analyzedbrowser or server?
            • 14.8.5.2. How much information will the server provide?
          • 14.8.6. Real-World Examples
            • 14.8.6.1. YubNub
          • 14.8.7. Code Example: AjaxPatterns Assistive Search Demo
          • 14.8.8. Alternatives
            • 14.8.8.1. Point-and-click
            • 14.8.8.2. Drag-And-Drop
          • 14.8.9. Related Patterns
            • 14.8.9.1. Submission Throttling
            • 14.8.9.2. Status Area
            • 14.8.9.3. Highlight
            • 14.8.9.4. Progress Indicator
            • 14.8.9.5. Browser-Side Cache
            • 14.8.9.6. Fat Client
            • 14.8.9.7. Live Search
            • 14.8.9.8. Suggestion
          • 14.8.10. Want To Know More?
        • 14.9. Live Form
          • 14.9.1. Goal Story
          • 14.9.2. Problem
          • 14.9.3. Forces
          • 14.9.4. Solution
          • 14.9.5. Real-World Examples
            • 14.9.5.1. WPLicense
            • 14.9.5.2. Betfair
            • 14.9.5.3. MoveableType Comment hack
          • 14.9.6. Code Example: WPLicense
          • 14.9.7. Related Patterns
            • 14.9.7.1. Microlink
            • 14.9.7.2. Live Search
            • 14.9.7.3. Suggestion
            • 14.9.7.4. Drilldown
            • 14.9.7.5. Progress Indicator
            • 14.9.7.6. One-Second Spotlight
      • 15. Page Architecture
        • 15.1. Drag-And-Drop
          • 15.1.1. Goal Story
          • 15.1.2. Problem
          • 15.1.3. Forces
          • 15.1.4. Solution
          • 15.1.5. Decisions
            • 15.1.5.1. What constraints will apply to the drag operation?
          • 15.1.6. Real-World Examples
            • 15.1.6.1. Magnetic Poetry
            • 15.1.6.2. Backbase Portal
            • 15.1.6.3. A9 Maps
          • 15.1.7. Code Example: Magnetic Poetry
          • 15.1.8. Alternatives
            • 15.1.8.1. Separate Editing Interface
          • 15.1.9. Related Patterns
            • 15.1.9.1. Sprite
            • 15.1.9.2. Portlet
            • 15.1.9.3. Slider
        • 15.2. Sprite
          • 15.2.1. Goal Story
          • 15.2.2. Problem
          • 15.2.3. Forces
          • 15.2.4. Solution
          • 15.2.5. Decisions
            • 15.2.5.1. What file format will the Sprite image be?
            • 15.2.5.2. Will the Sprite be animated?
          • 15.2.6. Real-World Examples
            • 15.2.6.1. DHTML Lemmings
            • 15.2.6.2. Google Maps
            • 15.2.6.3. Quek
          • 15.2.7. Code Example: DHTML Lemmings
          • 15.2.8. Alternatives
            • 15.2.8.1. Tiling
          • 15.2.9. Related Patterns
            • 15.2.9.1. Popup
            • 15.2.9.2. Drag-And-Drop
          • 15.2.10. Metaphor
          • 15.2.11. Want to Know More?
          • 15.2.12. Acknowledgments
        • 15.3. Popup
          • 15.3.1. Goal Story
          • 15.3.2. Problem
          • 15.3.3. Forces
          • 15.3.4. Solution
          • 15.3.5. Decisions
            • 15.3.5.1. How will the Popup look?
            • 15.3.5.2. How will the user open and close the Popup?
          • 15.3.6. Real-World Examples
            • 15.3.6.1. JSCalc
            • 15.3.6.2. Flickr
            • 15.3.6.3. Netflix
            • 15.3.6.4. Hoversearch
          • 15.3.7. Code Example: JSCalc
          • 15.3.8. Alternatives
            • 15.3.8.1. Portlet
            • 15.3.8.2. Microlink
          • 15.3.9. Related Patterns
            • 15.3.9.1. Sprite
            • 15.3.9.2. Drag-And-Drop
            • 15.3.9.3. Slider
          • 15.3.10. Metaphor
        • 15.4. Malleable Content
          • 15.4.1. Goal Story
          • 15.4.2. Problem
          • 15.4.3. Forces
          • 15.4.4. Solution
          • 15.4.5. Decisions
            • 15.4.5.1. How will users locate Malleable Content and open it up for editing?
            • 15.4.5.2. Will the Malleable Content be labelled? What auxiliary information will be included?
            • 15.4.5.3. What content will be marked as Malleable Content? How big will the Malleable Content be?
            • 15.4.5.4. How will the user stop editing content?
            • 15.4.5.5. Is it okay to have several Malleable Content blocks open for editing at one time?
          • 15.4.6. Real-World Examples
            • 15.4.6.1. Flickr
            • 15.4.6.2. Monket Calendar
            • 15.4.6.3. Tiddlywiki
            • 15.4.6.4. Thomas Baekdal's Business Card Creator
          • 15.4.7. Code Example: AjaxPatterns Wiki
          • 15.4.8. Alternatives
            • 15.4.8.1. Compound Edit
          • 15.4.9. Related Patterns
            • 15.4.9.1. Live Form
            • 15.4.9.2. Rich Text Editor
            • 15.4.9.3. Microlink
            • 15.4.9.4. One-Second Spotlight, One-Second Motion, and One-Second Mutation
            • 15.4.9.5. Highlight
          • 15.4.10. Metaphor
        • 15.5. Microlink
          • 15.5.1. Goal Story
          • 15.5.2. Problem
          • 15.5.3. Forces
          • 15.5.4. Solution
          • 15.5.5. Decisions
            • 15.5.5.1. What will happen to other content?
            • 15.5.5.2. How will Microlink be presented visually?
          • 15.5.6. Real-World Examples
            • 15.5.6.1. TiddlyWiki
            • 15.5.6.2. Tabtastic library
            • 15.5.6.3. Rpad
            • 15.5.6.4. Gmail
          • 15.5.7. Code Example: TiddlyWiki
          • 15.5.8. Related Patterns
            • 15.5.8.1. Malleable Content
            • 15.5.8.2. "One-Second" visual effects
            • 15.5.8.3. Drilldown
            • 15.5.8.4. Popup
            • 15.5.8.5. Live Form
        • 15.6. Portlet
          • 15.6.1. Goal Story
          • 15.6.2. Problem
          • 15.6.3. Forces
          • 15.6.4. Solution
          • 15.6.5. Decisions
            • 15.6.5.1. Will users be able to move Portlets around?
          • 15.6.6. Real-World Examples
            • 15.6.6.1. Claude Hussenet's Portal
            • 15.6.6.2. Google Homepage
            • 15.6.6.3. Backbase
            • 15.6.6.4. Dobrado
          • 15.6.7. Code Example: Claude Hussenet's Portal
          • 15.6.8. Alternatives
            • 15.6.8.1. Tabbed Browsing
          • 15.6.9. Related Patterns
            • 15.6.9.1. Periodic Refresh
            • 15.6.9.2. Distributed Events
            • 15.6.9.3. Drilldown
            • 15.6.9.4. Live Form
            • 15.6.9.5. Cross-Domain Proxy
          • 15.6.10. Metaphor
          • 15.6.11. Acknowledgments
        • 15.7. Status Area
          • 15.7.1. Goal Story
          • 15.7.2. Problem
          • 15.7.3. Forces
          • 15.7.4. Solution
          • 15.7.5. Decisions
            • 15.7.5.1. How will you size the Status Area? What if it overflows?
            • 15.7.5.2. How will you structure the Status Area's content?
          • 15.7.6. Real-World Examples
            • 15.7.6.1. BetFair
            • 15.7.6.2. Lace Chat
          • 15.7.7. Code Refactoring: AjaxPatterns Status Wiki
          • 15.7.8. Alternatives
            • 15.7.8.1. Popup
            • 15.7.8.2. Browser Status Bar
          • 15.7.9. Related Patterns
            • 15.7.9.1. Periodic Refresh
          • 15.7.10. Metaphor
        • 15.8. Update Control
          • 15.8.1. Goal Story
          • 15.8.2. Problem
          • 15.8.3. Forces
          • 15.8.4. Solution
          • 15.8.5. Real-World Examples
            • 15.8.5.1. Digg Spy
            • 15.8.5.2. Slide
            • 15.8.5.3. WBIR
          • 15.8.6. Code Example: Digg Spy
          • 15.8.7. Related Patterns
            • 15.8.7.1. Periodic Refresh
            • 15.8.7.2. HTTP Streaming
          • 15.8.8. Metaphor
          • 15.8.9. Acknowledgments
        • 15.9. Virtual Workspace
          • 15.9.1. Goal Story
          • 15.9.2. Problem
          • 15.9.3. Forces
          • 15.9.4. Solution
          • 15.9.5. Decisions
            • 15.9.5.1. How will you handle panning?
            • 15.9.5.2. How will the view appear initially?
            • 15.9.5.3. What do you display while a region is being repopulated?
            • 15.9.5.4. How will you handle changes to the existing view?
          • 15.9.6. Real-World Examples
            • 15.9.6.1. map.search.ch
            • 15.9.6.2. OpenRico Search Demo
            • 15.9.6.3. Giant-Ass Image Viewer (GSV) library
            • 15.9.6.4. Dunstan Orchard's blog
          • 15.9.7. Code Refactoring: AjaxPatterns OpenRico Search
          • 15.9.8. Alternatives
            • 15.9.8.1. Virtual Magnifying Glass
          • 15.9.9. Related Patterns
            • 15.9.9.1. Browser-Side Cache
            • 15.9.9.2. Predictive Fetch
            • 15.9.9.3. Guesstimate
            • 15.9.9.4. Multi-Stage Download
            • 15.9.9.5. Drag-And-Drop
            • 15.9.9.6. Slider
            • 15.9.9.7. Unique URLs
          • 15.9.10. Metaphor
          • 15.9.11. Want to Know More?
          • 15.9.12. Acknowledgments
      • 16. Visual Effects
        • 16.1. One-Second Spotlight
          • 16.1.1. Goal Story
          • 16.1.2. Problem
          • 16.1.3. Forces
          • 16.1.4. Solution
          • 16.1.5. Decisions
            • 16.1.5.1. What events will trigger a spotlight?
            • 16.1.5.2. What color will be used?
            • 16.1.5.3. How long should the spotlight last? How long will each transition be?
          • 16.1.6. Real-World Examples
            • 16.1.6.1. 37signals Backpack
            • 16.1.6.2. chat.app
            • 16.1.6.3. Digg Spy
            • 16.1.6.4. Coloir
            • 16.1.6.5. Odeo
            • 16.1.6.6. Scriptaculous library
            • 16.1.6.7. Fade Anything Technique (FAT) library
          • 16.1.7. Code Refactoring: AjaxPatterns Spotlight Time
            • 16.1.7.1. Hand-built shift effect
            • 16.1.7.2. Fading with Scriptaculous
          • 16.1.8. Alternatives
            • 16.1.8.1. One-Second Mutation and One-Second Motion
          • 16.1.9. Related Patterns
            • 16.1.9.1. Periodic Refresh
            • 16.1.9.2. Timeout
          • 16.1.10. Metaphor
          • 16.1.11. Acknowledgments
        • 16.2. One-Second Mutation
          • 16.2.1. Goal Story
          • 16.2.2. Problem
          • 16.2.3. Forces
          • 16.2.4. Solution
          • 16.2.5. Decisions
          • 16.2.6. Real-World Examples
            • 16.2.6.1. TiddlyWiki
            • 16.2.6.2. Scriptaculous library
            • 16.2.6.3. DHTML Lemmings
          • 16.2.7. Code Example: TiddlyWiki
          • 16.2.8. Alternatives
            • 16.2.8.1. One-Second Spotlight and One-Second Motion
          • 16.2.9. Related Patterns
            • 16.2.9.1. Sprite
          • 16.2.10. Metaphor
          • 16.2.11. Acknowledgments
        • 16.3. One-Second Motion
          • 16.3.1. Goal Story
          • 16.3.2. Problem
          • 16.3.3. Forces
          • 16.3.4. Solution
          • 16.3.5. Decisions
            • 16.3.5.1. What events will trigger a motion effect?
            • 16.3.5.2. What will the element do when it reaches its destination?
          • 16.3.6. Real-World Examples
            • 16.3.6.1. Scriptaculous library
            • 16.3.6.2. TiddlyWiki
            • 16.3.6.3. Backbase Portal
            • 16.3.6.4. DHTML Lemmings
            • 16.3.6.5. MS-Windows
          • 16.3.7. Code Example: Scriptaculous Effects
          • 16.3.8. Alternatives
            • 16.3.8.1. One-Second Spotlight and One-Second Mutation
          • 16.3.9. Related Patterns
            • 16.3.9.1. Sprite
            • 16.3.9.2. Guesstimate
          • 16.3.10. Metaphor
        • 16.4. Highlight
          • 16.4.1. Goal Story
          • 16.4.2. Problem
          • 16.4.3. Forces
          • 16.4.4. Solution
          • 16.4.5. Decisions
            • 16.4.5.1. How will the Highlight look?
            • 16.4.5.2. How will the Highlight appear and disappear?
          • 16.4.6. Real-World Examples
            • 16.4.6.1. Gmail
            • 16.4.6.2. A9
            • 16.4.6.3. Teacher!
            • 16.4.6.4. Whitespace
          • 16.4.7. Code Example: AjaxPatterns Wiki
          • 16.4.8. Related Patterns
            • 16.4.8.1. Status Area
            • 16.4.8.2. One-Second Spotlight
          • 16.4.9. Metaphor
      • 17. Functionality
        • 17.1. Lazy Registration
          • 17.1.1. Goal Story
          • 17.1.2. Problem
          • 17.1.3. Forces
          • 17.1.4. Solution
          • 17.1.5. Decisions
            • 17.1.5.1. What kind of data will the profile contain?
            • 17.1.5.2. How can the profile be accumulated?
            • 17.1.5.3. How much data should be stored in cookies?
          • 17.1.6. Real-World Examples
            • 17.1.6.1. Memeflow
            • 17.1.6.2. Blummy
            • 17.1.6.3. Kayak
            • 17.1.6.4. Palmsphere
            • 17.1.6.5. Amazon.com
          • 17.1.7. Code Example: AjaxPatterns Shop Demo
            • 17.1.7.1. Retrieval of categories and items
            • 17.1.7.2. Cart management
            • 17.1.7.3. Mailing cart contents
            • 17.1.7.4. Tracking favorite categories
            • 17.1.7.5. Verifying password and email
          • 17.1.8. Related Patterns
            • 17.1.8.1. Direct Login
            • 17.1.8.2. Live Form
            • 17.1.8.3. Timeout
            • 17.1.8.4. Guesstimate
          • 17.1.9. Metaphor
          • 17.1.10. Want to Know More?
          • 17.1.11. Acknowledgments
        • 17.2. Direct Login
          • 17.2.1. Goal Story
          • 17.2.2. Problem
          • 17.2.3. Forces
          • 17.2.4. Solution
          • 17.2.5. Decisions
            • 17.2.5.1. What hashing algorithm will be used?
            • 17.2.5.2. How will you manage the one-time seed?
          • 17.2.6. Real-World Examples
            • 17.2.6.1. NetVibes
            • 17.2.6.2. Protopage
            • 17.2.6.3. Treehouse
          • 17.2.7. Code Examples: Ajax Login Demo
          • 17.2.8. Related Patterns
            • 17.2.8.1. Lazy Registration
            • 17.2.8.2. Host-Proof Hosting
            • 17.2.8.3. Timeout
          • 17.2.9. Acknowledgments
        • 17.3. Host-Proof Hosting
          • 17.3.1. Goal Story
          • 17.3.2. Problem
          • 17.3.3. Forces
          • 17.3.4. Solution
          • 17.3.5. Decisions
            • 17.3.5.1. What encryption algorithm and framework will be used?
            • 17.3.5.2. When will the pass-phrase be requested?
          • 17.3.6. Real-World Examples
          • 17.3.7. Code Example: Host-Proof-Hosting Proof-Of-Concept
          • 17.3.8. Alternatives
            • 17.3.8.1. Richer Plugin
          • 17.3.9. Related Patterns
            • 17.3.9.1. Direct Login
            • 17.3.9.2. Timeout
          • 17.3.10. Metaphor
          • 17.3.11. Want to Know More?
          • 17.3.12. Acknowledgments
        • 17.4. Timeout
          • 17.4.1. Goal Story
          • 17.4.2. Problem
          • 17.4.3. Forces
          • 17.4.4. Solution
          • 17.4.5. Decisions
            • 17.4.5.1. How long will the Timeout period be?
            • 17.4.5.2. How will Timeout affect the user interface?
          • 17.4.6. Real-World Examples
            • 17.4.6.1. Lace Chat
            • 17.4.6.2. Pandora
            • 17.4.6.3. Session Warning Demo
            • 17.4.6.4. Operating system Timeouts
          • 17.4.7. Code Refactoring: AjaxPatterns Timeout Wiki
            • 17.4.7.1. Introducing Timeout to the wiki
            • 17.4.7.2. Initial refactoring: unconditional Timeout
            • 17.4.7.3. Warning that Timeout is pending
            • 17.4.7.4. Monitoring mouse movements
          • 17.4.8. Related Patterns
            • 17.4.8.1. Heartbeat
            • 17.4.8.2. Periodic Refresh
            • 17.4.8.3. Progress Indicator
            • 17.4.8.4. Direct Login
            • 17.4.8.5. Status Area
            • 17.4.8.6. Popup
          • 17.4.9. Metaphor
        • 17.5. Heartbeat
          • 17.5.1. Goal Story
          • 17.5.2. Problem
          • 17.5.3. Forces
          • 17.5.4. Solution
          • 17.5.5. Decisions
            • 17.5.5.1. How will you maintain user records?
            • 17.5.5.2. What, if anything, will cause the browser application to stop sending Heartbeats?
            • 17.5.5.3. How much time between Heartbeats? How much delay until a user is declared inactive?
          • 17.5.6. Real-World Examples
          • 17.5.7. Code Refactoring: AjaxPatterns Heartbeat Wiki
          • 17.5.8. Related Patterns
            • 17.5.8.1. Timeout
            • 17.5.8.2. Submission Throttling
          • 17.5.9. Metaphor
          • 17.5.10. Want to Know More?
        • 17.6. Unique URLs
          • 17.6.1. Goal Story
          • 17.6.2. Problem
          • 17.6.3. Forces
          • 17.6.4. Solution
          • 17.6.5. Decisions
            • 17.6.5.1. How will you support search engine indexing?
            • 17.6.5.2. What will be the polling interval?
            • 17.6.5.3. What state differences warrant Unique URLs?
            • 17.6.5.4. What will the URLs look like?
          • 17.6.6. Real-World Examples
            • 17.6.6.1. PairStairs
            • 17.6.6.2. Dojo binding library
            • 17.6.6.3. Really Simple History library
          • 17.6.7. Code Refactoring: AjaxPatterns Unique URL Sum
            • 17.6.7.1. Unique URL Sum Demo
            • 17.6.7.2. Polling URL Sum Demo
            • 17.6.7.3. IFrame Sum Demo
            • 17.6.7.4. Full IFrame Sum Demo
          • 17.6.8. Alternatives
            • 17.6.8.1. Occasional refresh
            • 17.6.8.2. "Here" link
          • 17.6.9. Want to Know More?
          • 17.6.10. Acknowledgments
    • V. Development Patterns
      • 18. Diagnosis
        • 18.1. Logging
          • 18.1.1. Developer Story
          • 18.1.2. Problem
          • 18.1.3. Solution
          • 18.1.4. Decisions
            • 18.1.4.1. Will you log during production?
            • 18.1.4.2. How will you change log settings between development and production?
          • 18.1.5. Tool Support
            • 18.1.5.1. Lumberjack
            • 18.1.5.2. fvLogger
            • 18.1.5.3. log4js
            • 18.1.5.4. Mochikit
          • 18.1.6. Code Example: Using Lumberjack
        • 18.2. Debugging
          • 18.2.1. Developer Story
          • 18.2.2. Problem
          • 18.2.3. Solution
          • 18.2.4. Tool Support
            • 18.2.4.1. Venkman
            • 18.2.4.2. Microsoft Script Debugger
            • 18.2.4.3. JavaScript HTML Debugger
        • 18.3. DOM Inspection
          • 18.3.1. Developer Story
          • 18.3.2. Problem
          • 18.3.3. Solution
          • 18.3.4. Tool Support
            • 18.3.4.1. Firefox DOM Inspector
            • 18.3.4.2. Firefox Web Developer Extension
            • 18.3.4.3. View Rendered Source
            • 18.3.4.4. IE Developer Toolbar
            • 18.3.4.5. IEDocMon
            • 18.3.4.6. Mouseover DOM Inspector
        • 18.4. Traffic Sniffing
          • 18.4.1. Developer Story
          • 18.4.2. Problem
          • 18.4.3. Solution
          • 18.4.4. Tool Support
            • 18.4.4.1. XMLHttpRequest Tracing and XMLHttpRequest Debugging
            • 18.4.4.2. Fiddler
            • 18.4.4.3. FlangeLib
          • 18.4.5. Code Example: Using XMLHttpRequest Tracing
          • 18.4.6. Related Patterns
            • 18.4.6.1. Logging
      • 19. Testing
        • 19.1. Simulation Service
          • 19.1.1. Developer Story
          • 19.1.2. Problem
          • 19.1.3. Solution
          • 19.1.4. Decisions
            • 19.1.4.1. How will you switch between different services?
          • 19.1.5. Code Example: Simulation Service
          • 19.1.6. Related Patterns
            • 19.1.6.1. Service Test
          • 19.1.7. Want to Know More?
        • 19.2. Browser-Side Test
          • 19.2.1. Developer Story
          • 19.2.2. Problem
          • 19.2.3. Solution
          • 19.2.4. Tool Support
            • 19.2.4.1. Scriptaculous testing framework
            • 19.2.4.2. JsUnit framework (Hieatt)
            • 19.2.4.3. JsUnit Framework (Schaible)
          • 19.2.5. Code Example: Using Scriptaculous Unit-Testing
          • 19.2.6. Related Patterns
            • 19.2.6.1. Service Test
            • 19.2.6.2. Logging
        • 19.3. Service Test
          • 19.3.1. Developer Story
          • 19.3.2. Problem
          • 19.3.3. Solution
          • 19.3.4. Tool Support
            • 19.3.4.1. Ruby Net::HTTP
            • 19.3.4.2. Jakarta HTTPClient
            • 19.3.4.3. PHP HTTPClient
          • 19.3.5. Code Example: Service Test
          • 19.3.6. Related Patterns
            • 19.3.6.1. Simulation Service
            • 19.3.6.2. Browser-Side Test
        • 19.4. System Test
          • 19.4.1. Developer Story
          • 19.4.2. Problem
          • 19.4.3. Solution
          • 19.4.4. Tool Support
            • 19.4.4.1. GhostTrain
            • 19.4.4.2. Watir
            • 19.4.4.3. Selenium
            • 19.4.4.4. HTTPUnit
            • 19.4.4.5. DojoToolkit
          • 19.4.5. Code Example: Using Scriptaculous GhostTrain
          • 19.4.6. Related Patterns
            • 19.4.6.1. Browser-Side Test
            • 19.4.6.2. Simulation Service
          • 19.4.7. Want to Know More?
    • VI. Appendixes
      • A. Ajax Frameworks and Libraries
        • A.1. JavaScript Multipurpose Frameworks
          • A.1.1. AjaxFace (from 2005)
          • A.1.2. Backbase (from 2003)
          • A.1.3. Bindows (from 2003)
          • A.1.4. Dojo (from September, 2004)
          • A.1.5. eBusiness Applications (EBA) Ajax Components (from 2002)
          • A.1.6. Engine for Web Applications (from 2002)
          • A.1.7. Framework for RESTful JavaScript (Freja) (from 2006)
          • A.1.8. Mochikit (from 2005)
          • A.1.9. OpenRico (from May, 2005; based on earlier proprietary framework)
          • A.1.10. Plex Toolkit
          • A.1.11. Prototype
          • A.1.12. qooxdoo (from May, 2005)
          • A.1.13. Script.aculo.us (from 2005)
          • A.1.14. SmartClient (from 2000)
          • A.1.15. ThyAPI (from end of 2004)
          • A.1.16. TIBCO General Interface (from 2001)
          • A.1.17. Interactive Website Framework (from May 2005)
          • A.1.18. Zimbra AjaxTK
        • A.2. JavaScript Remoting Frameworks
          • A.2.1. AjaxCaller (from May 2005)
          • A.2.2. Ajax Client Engine (ACE) (from December 2005)
          • A.2.3. AjaxGear (from November 2005)
          • A.2.4. AJFORM (from June 2005)
          • A.2.5. HTMLHttpRequest (from 2005)
          • A.2.6. JSMX (from Aug 2005)
          • A.2.7. LibXMLHttpRequest (from June 2003)
          • A.2.8. MAJAX (from August 2005)
          • A.2.9. RSLite
          • A.2.10. Sack (from May 2005)
          • A.2.11. Subsys_JsHttpRequest
          • A.2.12. XHConn (from April, 2005)
        • A.3. JavaScript Effects Frameworks
          • A.3.1. Fade Anything Technique (FAT)
          • A.3.2. Moo.fx (from Oct 2005)
        • A.4. JavaScript Flash Frameworks
          • A.4.1. AMFPHPKit
          • A.4.2. Flash JavaScript Integration Kit
          • A.4.3. Stream (from July, 2005)
        • A.5. JavaScript XML Frameworks
          • A.5.1. Google AJAXSLT (from June 2005)
          • A.5.2. Sarissa (from February, 2003)
        • A.6. JavaScript Specialized Frameworks
          • A.6.1. Drag-Drop
          • A.6.2. Giant-Ass Image Viewer (GSV)
        • A.7. Multilanguage Ajax Frameworks
          • A.7.1. Cross-Platform Asynchronous INterface Toolkit (CPAINT) (from May 2005)
          • A.7.2. JavaScript Object Notation (JSON) and JSON-RPC
          • A.7.3. JavaScript Remote Scripting (JSRS) (from 2000)
          • A.7.4. Rialto: Rich Internet AppLication TOolkit
          • A.7.5. SAJAX (from March 2005)
          • A.7.6. ZKAjax/XUL Web Framework
        • A.8. C++ Ajax Frameworks
          • A.8.1. Wt
        • A.9. ColdFusion Ajax Frameworks
          • A.9.1. AjaxCFC
          • A.9.2. JSMX (from August 2005)
        • A.10. .NET Ajax Frameworks
          • A.10.1. Ajax.NET for ASP.NET 1.x/2.0
          • A.10.2. Anthem.NET for ASP.NET 1.x/2.0
          • A.10.3. AjaxAspects
          • A.10.4. Atlas (from late 2005)
          • A.10.5. Bitkraft for ASP.NET
          • A.10.6. ComfortASP.NET for ASP.NET 1.1/2.0
          • A.10.7. MagicAjax.NET (from September 2005)
          • A.10.8. MonoRail (from May 2005)
          • A.10.9. WebORB for .NET (from August 2005)
          • A.10.10. zumiPage
        • A.11. Java Ajax Frameworks
          • A.11.1. AjaxAnywhere (from September 2005)
          • A.11.2. AJAX JSP Tag Library
          • A.11.3. AJAX Java Server Faces Framework
          • A.11.4. Direct Web Remoting (DWR) (from 2005)
          • A.11.5. Echo 2 (from March 2005)
          • A.11.6. Guise
          • A.11.7. ICEfaces
          • A.11.8. JSON-RPC-Java (from April 2004)
          • A.11.9. JSP Controls Tag Library (from December 2005)
          • A.11.10. jWic
          • A.11.11. Struts-Layout
          • A.11.12. SWATO (from 2005)
          • A.11.13. Tacos Tapestry Components (from December 2005)
          • A.11.14. ThinkCAP JX
          • A.11.15. WebORB for Java (from August 2005)
          • A.11.16. WidgetServer (from 2004)
        • A.12. Lisp Ajax Frameworks
          • A.12.1. CL-Ajax
        • A.13. Perl Ajax Frameworks
          • A.13.1. CGI::AjaxExport Perl Methods to JavaScript for Ajax
          • A.13.2. HTML::PrototypeGenerate HTML and JavaScript for the Prototype Library
        • A.14. PHP Ajax Frameworks
          • A.14.1. AJASON
          • A.14.2. AjaxAC (from April, 2005)
          • A.14.3. Cajax
          • A.14.4. HTS Web Application Framework
          • A.14.5. JPSpan
          • A.14.6. PEAR::HTML::Ajax
          • A.14.7. Pipeline
          • A.14.8. Symfony
          • A.14.9. XAJAX
          • A.14.10. XOAD (formerly NAJAX)
        • A.15. Python Ajax Frameworks
          • A.15.1. CrackAJAX
          • A.15.2. Turbo Gears
        • A.16. Ruby Ajax Frameworks
          • A.16.1. Ruby On Rails
      • B. Setting Up the Code Examples
      • C. Patterns and Pattern Languages
      • D. References
    • About the Author
    • Colophon
    • SPECIAL OFFER: Upgrade this ebook with OReilly

Dodaj do koszyka Ajax Design Patterns. Creating Web 2.0 Sites with Programming and Usability Patterns

Code, Publish & WebDesing by CATALIST.com.pl



(c) 2005-2024 CATALIST agencja interaktywna, znaki firmowe należą do wydawnictwa Helion S.A.