COMPARISON OF HTML5 AND (GOOGLE) GEARS

Comparison of HTML5 and (Google) Gears

Abstract

In general the web application enabling offline technologies Gears (formerly Google Gears) and the current HTML5 spec should be introduced and compared. It is important that the text not used information published after 2009.09.01 for example Google dropped Gears few weeks ago this should be mentioned in the text since this information was released after the 2009.09.01!

Table of contents

Abstract2

Introduction4

Explanation5

Evaluation HTML56

Developers6

History9

Google Gears9

Local storage10

LocalStorage and sessionStorage10

The storage event11

Gears LocalServer12

WebKit libs16

References18

Comparison of HTML5 and (Google) Gears

Introduction

HTML is the language that powers the Web in many respects, as the lingua franca that Web browsers are expected to be able to render. HTML has had unprecedented levels of success, and the uptake is all the more surprising when you realise that it was only invented in 1990, and few people knew about it before 1993. (Richard L. Brandt, 2009, 34-67)

In fact, although HTML has changed relatively little since those early days, the history of HTML is rather cloudy. However, with a little detective work on the Web, it is possible to reconstruct most of the events that led to the creation and subsequent deployment and acception of HTML. HTML5 is the proposed next standard for HTML 4.01, XHTML 1.0 and DOM Level 2 HTML. It aims to reduce the need for proprietary plug-in-based rich internet application (RIA) technologies such as Adobe Flash, Microsoft Silverlight, Apache Pivot, and Sun JavaFX.

The ideas behind HTML5 were pioneered in 2004 by the WHATWG; HTML5 incorporates Web Forms 2.0, another WHATWG specification. The HTML5 specification was adopted as the starting point of the work of the new HTML working group of the W3C in 2007. This working group published the First Public Working Draft of the specification on January 22, 2008.[3] The specification is an ongoing work, and is expected to remain so for many years, although parts of HTML5 are going to be finished and implemented in browsers before the whole specification reaches final Recommendation status

The idea that HTML's evolution should be reopened was tested at a W3C workshop in 2004, where some of the principles that underlie the HTML5 work (described below), as well as the aforementioned early draft proposal covering just forms-related features, were presented to the W3C jointly by Mozilla and Opera. The proposal was rejected on the grounds that the proposal conflicted with the previously chosen direction for the Web's evolution; the W3C staff and membership voted to continue developing XML-based replacements instead. (Richard L. Brandt, 2009, 34-67)

Explanation

Shortly thereafter, Apple, Mozilla, and Opera jointly announced their intent to continue working on the effort under the umbrella of a new venue called the WHATWG. A public mailing list was created, and the draft was moved to the WHATWG site. The copyright was subsequently amended to be jointly owned by all three vendors, and to allow reuse of the specification.

The WHATWG was based on several core principles, in particular that technologies need to be backwards compatible that specifications and implementations need to match even ...