#localserver

Part-1

Let’s look LocalServer first,

The LocalServer will allow to cache URL, Cached URLs served from the user’s disk. For security gear allows to access pages that have the same scheme, host, and port as the current domain.

First you have to create localserver object using gear factory. var localServer = google.gears.factory.create('beta.localserver', '1.0'); // version is optional There are two ways defined in gear API to manage URL cache. 1) ResourceStore :- The ResourceStore is deal with URLs. It will capture URLs using JavaScript, like html, JavaScript, images etc. A ResourceStore is a container of cached URLs. ResourceStore is better for capturing one file or array of files.

// creating store with name 'mbanph' var store = localServer.createStore('mbanph'); // Capture this page and the js library you need to run offline. store.capture(['include.js','style.css','../gears_init.js'], function(url, success, captureId){});

2) ManagedResourceStore :- The ManagedResourceStore is deal with URLs which defined in mainfest file, Gears captures and updates applications resource automatically. If you have lots of file to capture than better to use ManagedResourceStore option to capture resources.

content in offline.json file. { "betaManifestVersion": 1, "version": "version 1.0", "entries": [ { "url": "gearsTest.html"}, { "url": "include.js"}, { "url": "style.css"}, { "url": "../gears_init.js"} { "url": "checkOffline.js"}, { "url": "../images/logo.png"}, { "url": "../images/background.png"}, { "url": "../terms.pdf"} ] }

var store = localServer.createManagedStore('mbanph'); store.manifestUrl = '../offline.json'; store.checkForUpdate();

With ResourceStore and ManagedResourceStore you can create, open and delete store. other API related information you can find out here.