Caching

From IAB Wiki
(Difference between revisions)
Jump to: navigation, search
 
Line 3: Line 3:
 
normally done in two places: in the user's browser and on proxy servers. When a user makes a
 
normally done in two places: in the user's browser and on proxy servers. When a user makes a
 
request for a Web element, the browser looks into its own cache for the element; then a proxy, if
 
request for a Web element, the browser looks into its own cache for the element; then a proxy, if
any; followed by the intended server <span class="plainlinks">[http://www.cashadvance-loans.net/ <span style="color:black;font-weight:normal; text-decoration:none!important; background:none!important; text-decoration:none;">cash advance loans</span>]. Caching is done to reduce redundant network traffic,
+
any; followed by the intended server. Caching is done to reduce redundant network traffic,
 
resulting in increased overall efficiency of the Internet.
 
resulting in increased overall efficiency of the Internet.

Latest revision as of 21:25, 20 November 2012

The process of copying a Web element (page or ad) for later reuse. On the Web, this copying is normally done in two places: in the user's browser and on proxy servers. When a user makes a request for a Web element, the browser looks into its own cache for the element; then a proxy, if any; followed by the intended server. Caching is done to reduce redundant network traffic, resulting in increased overall efficiency of the Internet.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox