Next:
The WAP Trap
Up:
The Lightweight & Efficient
Previous:
Preview of Coming Attractions
Contents
Index
LEAPing Over Closed Solutions
Subsections
The WAP Trap
Introduction
The Wireless Application Protocol (WAP)
Characteristics of Successful Protocols
About this Document
Alternative Formats
Acknowledgments
Conflict of Interest Disclosure
WAP - A Procedural Fraud
Not Open in Terms of Development and Maintenance
No Assurance of Availability and Stability
Not Patent-Free
No Legitimacy as a Standard
WAP - A Technical Failure
User Interface Assumptions
Extreme Accommodation to Existing Networks
Excessive Re-Invention in the Name of Wireless
Vulnerable Wireless Transport Layer Security (WTLS)
Bungled Protocol Number Assignment
WAP - A Basic Misconception
The Wrong Answer Initially: Mobile Web Browsing
The Right Answer Initially: Mobile Messaging
Unsupported Claims
Not Device-Independent
Limited Web Browsing Capabilities
Existing Technology Adequate
Voice Interface Adequate
Conclusion: WAP is a Trap
Preventing the Harm of WAP
Reform the WAP Forum
Spread the Word about the WAP Fraud
Reject WAP at Engineering Level
Reject WAP at Consumer Level
Adopt an Alternative to WAP
LEAP: One Alternative To WAP
LEAP: One Alternative to WAP
Introduction
The WAP Trap
About this Document
The Need for Efficiency
LEAP: The Lightweight & Efficient Application Protocols
A Brief History of LEAP
Technical Overview of LEAP
Layering of LEAP
ESRO, Efficient Short Remote Operations
EMSD, Efficient Mail Submission and Delivery
Initial Focus: Mobile Messaging
Processes and Procedures
Freedom from Patents
RFC Publication
Open Maintenance Organizations
Comparison of LEAP to WAP
Patent Restrictions
Openness of Publication
Openness of Maintenance
Technical Deficiencies
Initial Focus
Hype versus Reality
Making LEAP Widespread
Other Alternatives to WAP
Summary
The LEAP Manifesto
WAP Scraps
Introduction
Claiming the Day
Mobile Web Browsing: An Open Industry Model
About this Document
Acknowledgments
Conflict of Interest Disclosure
Mobile Web Browsing: Past, Present and Future
The Past: WAP
The Present: XHTML
The Importance of Efficiency
The Future: XHTML + LEAP
Invitation to Participate
WAP: A Salvage Operation
Engineering Salvage: Scrapping WAP Layer by Layer
Business Salvage: Cutting Financial Losses
Psychological Salvage: Saving Face
In Pursuit of Integrity
The WAP Hype Machine Fraud
Protocol Integrity
Engineering Integrity
Operation Whiteberry
Introduction
The Problem
The Solution
Free Protocols Foundation Endorsement of Operation WhiteBerry
Mobile Messaging Requirements
The BlackBerry Solution
How BlackBerry Works
BlackBerry: Mobile Messaging Confirmation
BlackBerry: A Closed Solution
BlackBerry: Not All Things to All People
Strategic Myopia: More Closed Solutions
The WhiteBerry Solution
Technological Components of WhiteBerry
The Unifying Component: A Set of Open Protocols
The Key to WhiteBerry: The LEAP Protocols
How WhiteBerry Works
Putting Everything Together for the End User
Technical Challenges & Responses
A Word About Networks
WhiteBerry versus BlackBerry
WhiteBerry Patent Resistance
Initial Development Framework
Open-Source Software Implementations
The MailMeAnywhere Development Forum
Initial Subscriber Services
Initial WhiteBerry Implementation
Mobile Messaging Security
BlackBerry Security
WhiteBerry Security
The Business Case for WhiteBerry
Immediate Opportunity: Installed Hardware Base
Precedents for Success
Shifting Opportunities: Winners & Losers
Business Conservativism
A Framework for Participation
Device Integration
Windows CE Enhancement
Palm OS Enhancement
Modem Integration
Challenge to Modem Manufacturers
Cell Phone Integration
Network Services Integration
Wireless ISP Integration
Network Operator Business Practices
Wireless Application Services Integration
Challenge to Application Service Providers
Systems and Solutions Integration
Message Center Integration
How to Participate
Beyond Operation WhiteBerry
Summary
Acknowledgments
