Interview with Mike Tsao of the Google Gears team
Written by on June 8th, 2007 in Ajax News.
To round out shark^H^H^H^H^HGears week we have an interview with Mike Tsao of the Google Gears team on the new Google Developer Podcast.
The interview gives us a view into how Gears was formed, and how the three initial components were created.
For example, the WorkerPooler that allows you to spawn a long running piece of JavaScript code in another thread came about as a solution to making sure that the browser wouldn’t hand while the Database component would write to SQLite.
In this interview you will learn:
- What Google Gears is at a high level
- How Google Gears came about
- The parts and pieces of Google Gears
- Information on the Datastore component (SQLite)
- Information on the ResourceStore and ManagedResourceStore components
- How the APIs look, and what should I be thinking about as I make my application offline
- How to handle versioning with Google Gears applications
- How the WorkerPool came about, and why we need to run JavaScript jobs in another thread
- The code contributions made back to the SQLite codebase (e.g. MATCH() added)
- The pain of finding the 90% case for syncing
- Thoughts on how the client is getting smarter
- How GWT supports Gears
- How Google Reader is using Gears
- How the UI fits in with offline behaviour
- The open source vision for Gears
- How other web platforms can access Gears
- Future ideas for Google Gears
You can download the episode directly, or subscribe to the show (click here for iTunes one-click subscribe).
Source: Ajaxian
Original Article: http://ajaxian.com/archives/interview-with-mike-tsao-of-the-google-gears-team