InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Enhanced Client Side Web Object Caching

IP.com Disclosure Number: IPCOM000031694D
Original Publication Date: 2004-Oct-05
Included in the Prior Art Database: 2004-Oct-05
Document File: 1 page(s) / 31K

Publishing Venue



Disclosed is a system designed to decrease the latency associated with downloading web content.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 75% of the total text.

Page 1 of 1

Enhanced Client Side Web Object Caching

Disclosed is a system designed to decrease the latency associated with downloading web content. A major problem associated with the latency associated to downloading web content is that the client caching scheme does not take advantage of resources that have already been downloaded. The proposed system aims to allow speedier download of web pages using an improved cache utilization scheme. The proposed system allows one to better utilize images and other "objects" in the cache of a web browser on the client side. The system might best be described by example. A user will download a web page. The web page will contain components such as images. These images will be named using the site name followed by an ID (e.g., ibmcomimg123456.gif) or some other naming scheme which identifies the housing page as well as a unique object identifier. Let us say that this original image was included in a page called page1.html. This same image is included in page2.html, which has not been accessed. In the current art, one would have to download a different image (even though it was already in cache). In the current invention, a caching facility (possibly enabled by a browser plug-in) will check and see if the object with the unique id resides on the client side. If it does, the browser will not download it from the server and instead use the cached entry. To make sure that a rogue site does not "spoof" images on the client side, images might...