The HTML5 draft adds a lot of exciting functionality to browsers. Perhaps the most exciting is adding a way for websites to be launched offline. For devices that have a high bandwidth and highly available connection, offline functionality might not be so important. For web applications running on mobile devices however, being able to launch offline can dramatically improve the web application experience.
AppCache support on the iPhone is still under development, but as of firmware 2.2.1, it is usable.
To make use of AppCache, a webpage must provide a "manifest" to the browser that lists all of the URLs that it intends to use. Creating an HTML5 manifest file is extremely simple, as shown by the following example.
CACHE MANIFEST
jsfile1.js
jsfile2.js
styles.css
/images/image1.png
/images/image2.png<html manifest="/sitemanifest">So now that you know how to create a manifest for your site, it's a good idea to know what's going on during page load. When the page is loaded for the first time, it will load as if there is no application cache associated with it. Once it has finished loading, the browser will fetch the manifest and all resources listed in it that have not already been fetched during page load. From this point on, any GET request that your page makes that is not listed in the manifest will fail, and any GET request that is listed in it will not hit the network, but will be satisfied by the cache. Once your page is loaded into AppCache, the next time the user loads the site, all of the resources will be served out of the cache. The only GET request done on page load will be for the manifest file, in order to see if it has changed. If it has changed, then all of the resources in it are fetched in the background and will be used the next time the user refreshes the page.
Stay tuned for the next post where we will share more about what we know about AppCache and how we use it on the Gmail team. Also, we'll be at Google I/O, May 27-28 in San Francisco presenting a session on how we use HTML5. We'll also be available at the Developer Sandbox, and we look forward to meeting you in person.
References
The HTML5 working draft:
http://dev.w3.org/html5/spec/Overview.html
Apple's MobileSafari documentation: http://developer.apple.com/webapps/docs/documentation/AppleApplications/Reference/SafariJSRef/DOMApplicationCache/DOMApplicationCache.html
Webkit Source Code:
http://trac.webkit.org/browser/trunk/WebCore/loader/appcache
Nice article, appcache indeed is a big step forward, but the Android browser (and desktop Chrome) does not support this feature so one has to use Gears Localserver (which offers similar but different functionality, with a different API) to do this on Android?
ReplyDeleteAppcache is supported in the latest Android 2.0 release.
ReplyDeleteMy phone is running Android 2.2 (Froyo).
ReplyDeleteIf I load up Google Mail in the web browser, disable my wireless radios, and then hit Refresh, I get an error.
On the iPhone 4, if I perform the same steps, Google Mail pops up via the files cached from the manifest, as expected.
I have submitted a bug report:
http://code.google.com/p/android/issues/detail?id=12128
muito bom..
ReplyDelete