Offline Storage Mechanisms Compared
Niall Kennedy has written an article on boosting Ajax performance using local storage. He discusses four different local storage mechanisms (cookies, Flash local shared object, userData in IE, and DOM storage in Firefox), mentions Dojo Storage as a way to abstract them and concludes that local storage is the next logical step for Ajax applications.
Kennedy describes the potentials of local storage for offline applications that could save changes locally and synchronize with the server when the connection is re-established. While this technique is nothing new, it is being rediscovered.
He continues by comparing and contrasting the four different types, describing their size limitations (from the 4KB for cookies to the 5MB for DOM Storage) and how they’re implemented. He concludes with:
In response to the article, there was some conversation on Ajaxian including a discussion of using browser cache. Brad Neuberg, of Dojo Storage, responded that there are two problems with using browser cache:
- the cache pinning problem
- application-created information (how to insert into the browser cache)