A patent application for Google Gears has recently been published at the US Patent and Trademark Office.
Google released Google Gears in May of 2007, to enable offline use of online applications. Gears is a browser plugin aimed at enabling people to use web based applications even when they aren’t connected to the internet. Imagine being able to write or edit emails or review RSS feeds or use a word processing program that was written to be used on the Web and use those programs offline, when you can’t be connected to the internet.
The Google Gears plugin has been released as an open source project by Google, and can be used with Google applications such as Google Reader and with Google Docs. It can also be used with applications from non-Google sites, such as Zoho Writer and Remember the Milk. There is also a special version of Google Gears for Mobile Web use.
The Google Gears API pages provide details on how Google Gears can be used to by other applications to bring offline usage for online applications.
Some recent speculation about Google Gears and how it might be used in the future is circulating on the Web:
- Why is Google not Deploying Gears Aggressively?
- Is a Google Operating System Built on Android, Gears in the Cards?
If you’ve looked deeply into how Google Gears works, the technical aspects described in the patent filing might not come as a surprise, but you may find them worth a look. If you haven’t been paying much attention to Google Gears, it might be time to start considering how it might help shape the future of computing.
The patent application is at:
Method and apparatus that enables a web-based client-server application to be used offline
Invented by Erik V. Arvidsson and Andrew J. Palay
US Patent Application 20080301221
Published December 4, 2008
Filed: May 30, 2007
One embodiment of the present invention provides a system that facilitates using a web-based client-server application offline.
During operation, the system receives a function call at an object within a browser that is executing on a client, wherein the function call is generated by the web-based client-server application and is directed to a communication layer on the client.
Next, the system determines an intended resource for the function call. The system also determines if the function call should be redirected to an alternate resource. If so, the system redirects the function call to the alternate resource. If not, the system forwards the function call to the intended resource.
Note that in some embodiments of the present invention, the entire system operates within the context of the browser.