One of the challenges in developing web applications is to make the application can still run as normal when the Internet connection is interrupted or relatively very slow. Web applications that are typically encountered during will 'strike' to work when the connection is lost.
Background of this problem, Google launched Google Gears technology, which allows you to still be able to run web applications when the Internet connection was lost. In other words, Google Gears browser problem when running a web application to maintain the availability of data and applications when internet connection is lost.
Background of this problem, Google launched Google Gears technology, which allows you to still be able to run web applications when the Internet connection was lost. In other words, Google Gears browser problem when running a web application to maintain the availability of data and applications when internet connection is lost.
In principle, Google Gears is implemented as a browser extension with the installation files of about 700 kb online consists of 3 main modules. All three modules include: LocalServer, Database and Workerpool.
LocalServer is responsible for managing the cache and provides a variety of resource applications (HTML, JavaScript, images and more) locally. Database functions to store data locally secra in a relational database with full search facilities. The WorkerPool function is to make web applications more responsive. Way, WorkerPool running processes that are consuming resources are asynchronous.
Gears is available for Windows, Windows Mobile (IE Mobile, Opera Mobile), Mac (Firefox, Safari), Linux and Android.
More about Google Gears :
- Introduction to Google Gears: Creating Off-Line Applications with Pre-built Components (Wrox Briefs)
- Google Gears API Blog
- Practical Ext JS Projects with Gears (Practical Projects)
0 comments:
Post a Comment