• 1
• 2
• 3
• 4
• 5

access account accountdetails accountdetailsinfo accountinfo accountlist accountnumber accounts action adi ajax apache apex api app appendix application applications architecture asynccallback axis background browser build button buttonfetch buttons cache call called calls case caught change ci class classes click clicklistener client code compile component components composite configuration connection contact contactinfo contacts continue create creates creating data database define demo deploy describe description details display displayed download eclipse edit effectively entry excerpt execute executes experience extends extension fetch fetched figure file final finally functionality gears getaccounts google guide gwt hit home html implement implementation implemented implements include information int integration interface internet java javascript layer lets libraries library list local log login main menubar method methods myapplication note object offline onfailurethrowable online onsuccessobject page pages panel point populate port pretty private procedure programming provide public queries query read reader recall remember remote result retrieve retrieving return row rpc running salesforce salesforcecom section select sender serializable server service services servlet sfservice shown shows simple simply software source sql stack start started store storing string switch synchronization table tables tomcat toolkit turn tutorial type types ui user values varchar version verticalpanel void web wiki words

Keyword Cloud Navigation Map

Introduction: Software as a Service goes Offline

Your company has a Web application that exposes some Salesforce.com data. How do you access this Web application when you're not online? Well, surprisingly the answer is no longer "you can't", as the recent hype around Google Gears has shown. What Google Gears does is provide an extension to your browser. This extension includes a tiny database engine, a cache, and a JavaScript library that lets your Web application make use of the database and cache even when not connected to the Web.

In effect, your browser can cache relevant Web application pages and data, and let you continue to navigate the Web application even when you're not online. You don't get the infamous " 404 page. A great example of this is implemented in Google's own RSS reader. As shown in Figure 1, it now provides a facility to "go offline."

Read Full Tutorial...