Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »


The Web Storage API includes two related mechanisms for persisting client-side data in a secure manner using the Document Object Model (DOM),  sessionStorage and localStorage. These objects were introduced in Windows Internet Explorer 8.


For versions of Windows Internet Explorer prior to version 8, persistent data storage is implemented by the userData behavior.

What is DOM Storage?

Web Storage is often compared to HTTP cookies.  Like cookies, Web developers can store per-session or domain-specific data as name/value pairs on the client using Web Storage.  However, unlike cookies, Web Storage makes it easier to control how information stored by one window is visible to another.

For example, a user might open two browser windows to buy airline tickets for two different flights. However, if the airline's Web application uses cookies to store its session state, information could "leak" from one transaction into the other, potentially causing the user to buy two tickets for the same flight without noticing.  As applications become more capable of offline behaviours, such as storing values locally for later return to the server, the potential for this sort of information "leak" becomes more prevalent.

Web Storage also offers significantly more disk space than cookies.  In Internet Explorer, cookies can store only 4 kilobytes (KB) of data.  This byte total can be one name/value pair of 4 KB, or it can be up to 20 name/value pairs that have a total size of 4 KB.  By comparison, Web Storage provides roughly 10 megabytes (MB) for each storage area.

Functionally, client storage areas are quite different from cookies.  Web Storage doesn't transmit values to the server with every request as cookies do, nor does the data in a local storage area ever expire.  And unlike cookies, it is easy to access individual pieces of data using a standard interface that has growing support among browser vendors.


Session storage is designed for scenarios where the user is carrying out a single transaction. The sessionStorage attribute of the window object maintains key/value pairs for all pages loaded during the lifetime of a single tab (for the duration of the top-level browsing context).  For example, a page might have a check box that the user selects to indicate that he wants insurance.


	<input type="checkbox" onchange=" = checked">     
	I want insurance on this trip. 
  • No labels