userData introduced by
Microsoft which limits the size to 64 KB
in 2002 adobe introduced Flash Cookies – knows
as Local Shared Storage, store up to 100
Brad Neuberg wrote
AMASS (AJAX MASSIVE STORAGE SYSTEM) and integrated it into the Dojo Toolkit(dojox.storage)
2007 google launched
Gears, open source browser plugin. Gears provided an API to an embedded SQL
Database based on SQLLite.
2010 google had
shifted all the efforts on gears to HTML5 standards.
Cookies were pretty much the only
way to store the data in a user’s browser in the traditional browsers. Cookies
offers only limited amount of storage spaces in the client side. It allows a
maximum of 4K or 4096 bytes. If user wanted to keep large data it should be
broken and keeps in chunks and managed programmatically.
Downsides of cookies
It will be attached to every request; it will be
slowing down the app needlessly sending the data again and again.
HTML 5 Web Storage – It is standardized by W3C consortium.
It’s a way for web pages to store named key/value pairs locally with the client
web browser. A web page can only access the data created by itself.
Unlike cookies these data never transmitted to the web server (unless you sent
programmatically). It supports large amount of data without affecting the
application performance. The storage limit is far larger at least 5 MB. It
supports 5 MB per site in Chrome, Firefox and Opera; 10 MB storage in IE, 25 MB
in blackberry 10 devices.
IE FIREFOX SAFARI CHROME OPERA IPHONE ANDROID
8.0+ 3.5+ 4.0+ 4.0+ 10.5+ 2.0+ 2.0+
Unlike cookies this can be accessed by both
the server and client; also web server cannot write directly to the web storage
it should be achievable through the client side scripting.
Web storage offers two different kind of
Local storage – persist permanently in the
client side, it persist after the browser is closed.
Session storage – per page per window and it
remain to the lifetime of window.