Dare Obasanjo writes:
It consists of three components
* LocalServer: Allows you to cache and serve application resources such as HTML pages, scripts, stylesheets and images from a local web server.
* Database: A relational database where the application can store data locally. The database supports both full-text and SQL queries.
* WorkerPool: Allows applications to perform I/O expensive tasks in the background and thus not lock up the browser. A necessary evil.
At first, this seemed like a lot to functionality being offered by Google Gears until I started trying to design how I’d take some of my favorite Web applications offline.