
Web 2.0 Architectures
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Content
- Intro
- Web 2.0 Architectures
- SPECIAL OFFER: Upgrade this ebook with O'Reilly
- Preface
- Why Web 2.0 Matters
- The Post That Led to This Book
- Developing Web 2.0 Patterns
- How to Use This Book
- Conventions Used in This Book
- Using Code Examples
- Safari® Books Online
- How to Contact Us
- Acknowledgments
- Duane's Acknowledgments
- James's Acknowledgments
- Dion's Acknowledgments
- 1. An Architect's View of the Web
- Looking for Web 2.0
- Common Web 2.0 Architecture Patterns
- Capturing Web 2.0 Knowledge with Patterns and Architecture
- About Architecture
- A Brief Introduction to Architectural Patterns
- A Brief Introduction to Models
- How to Use Models and Patterns
- 2. A Different View of the Internet
- Best Practices for Forensic Architecture
- Internet Aspects
- Basic Communications: TCP/IP
- Conversations: HTTP and More
- Security
- Content
- Text and data
- Presentation and scripting
- Graphics
- Multimedia
- Semantics
- 3. Dissecting Web 2.0 Examples
- DoubleClick and Google AdSense
- Applicable Web 2.0 Patterns
- Advertising in Context
- A Peek at the Future of Online Advertising
- Ofoto and Flickr
- Applicable Web 2.0 Patterns
- Collaboration and Tagging
- Akamai and BitTorrent
- Applicable Web 2.0 Patterns
- Alternate Solutions to Bandwidth
- MP3.com and Napster
- Applicable Web 2.0 Patterns
- Shifting Patterns and Costs of Music Distribution
- MP3.com and Napster Infrastructures
- Britannica Online and Wikipedia
- Applicable Web 2.0 Patterns
- From a Scholarly to a Collaborative Model
- Personal Websites and Blogs
- Applicable Web 2.0 Patterns
- Shifting to Blogs and Beyond
- Screen Scraping and Web Services
- Applicable Web 2.0 Patterns
- Intent and Interaction
- Content Management Systems and Wikis
- Applicable Web 2.0 Patterns
- Participation and Relevance
- Directories (Taxonomy) and Tagging (Folksonomy)
- Applicable Web 2.0 Patterns
- Supporting Dynamic Information Publishing and Finding
- More Hints for Defining Web 2.0
- Reductionism
- 4. Modeling Web 2.0
- A New Client/Server Model for Web 2.0
- Capabilities
- Services
- Connectivity/Reachability
- Paper as a transport mechanism
- USB storage as part of a network
- Client Applications/Runtimes
- Users
- Time Magazine's Person of the Year: You (and Web 2.0)
- 5. A Reference Architecture for Developers
- About Reference Architectures
- The Web 2.0 Reference Architecture
- The Resource Tier
- The Service Tier
- The Client Application Tier
- Architectural Models That Span Tiers
- Model-View-Controller (MVC)
- Service-Oriented Architecture (SOA)
- Consistent Object and Event Models
- 6. From Models to Patterns
- A Metamodel for Architectural Patterns
- Patterns
- Context
- Problem
- Solution
- Introduction to Concept Map Notation
- The Pattern Presentation Template
- Pattern
- Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- 7. Specific Patterns of Web 2.0
- The Service-Oriented Architecture Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Request/Response
- Request/Response via service registry
- Subscribe/Push
- Probe and Match
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- The Software as a Service (SaaS) Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- The Participation-Collaboration Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- The Asynchronous Particle Update Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure and Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Mashup Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- The Rich User Experience Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- An example
- Static Structure and Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- The Synchronized Web Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Collaborative Tagging Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Declarative Living and Tag Gardening Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Semantic Web Grounding Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Persistent Rights Management (PRM) Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- The Structured Information Pattern
- Also Known As
- Business Problem (Story)
- Context
- Derived Requirements
- Generalized Solution
- Static Structure
- Dynamic Behavior
- Implementation
- Business Problem (Story) Resolved
- Specializations
- Known Uses
- Consequences
- References
- Summary
- 8. Where Are We Going from Here?
- Web 2.0 Offshoots
- A Timeless Way to Build Software 2.0
- The Timeless Way of Building Software: Inspiration for the Next Generation of Web Software
- Creating Open Services That Last (and That Anyone Can Use)
- Web 2.0 into the Uncertain Future
- Index
- About the Authors
- Colophon
- SPECIAL OFFER: Upgrade this ebook with O'Reilly
System requirements
File format: ePUB
Copy protection: Adobe-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Install the free reader Adobe Digital Editions prior to download (see eBook Help).
- Tablet/smartphone (Android; iOS): Install the free app Adobe Digital Editions or the app PocketBook before downloading (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (not Kindle).
The file format ePub works well for novels and non-fiction books – i.e., „flowing” text without complex layout. On an e-reader or smartphone, line and page breaks automatically adjust to fit the small displays.
This eBook uses Adobe-DRM, a „hard” copy protection. If the necessary requirements are not met, unfortunately you will not be able to open the eBook. You will therefore need to prepare your reading hardware before downloading.
Please note: We strongly recommend that you authorise using your personal Adobe ID after installation of any reading software.
For more information, see our ebook Help page.