CACHE CONTROL FOR WEB APPLICATION RESOURCES

• US 20140006622A1
• Filed: 06/29/2012
• Published: 01/02/2014
• Est. Priority Date: 06/29/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: KAPLINGER, TODD E., MITCHELL, CHRISTOPHER C., TRUTY, GREGORY L., ZHANG, JIANJUN
• Granted Patent: US 9,043,469 B2
• Time in Patent Office: Days
• US Class Current: 709/226
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: H04L 47/78 Architectures of resource allocation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Cache control for Web application resources can include receiving a cache manifest for a Web application, wherein the cache manifest specifies a Web page of the Web application, and determining, using a processor, a resource that is required by the Web page. A closure collection can be built that includes the resource required by the Web page. A reference to the resource can be written to the cache manifest.

Claims

1. A method comprising:

generating a cache manifest for a Web application, wherein the cache manifest specifies a Web page of the Web application;

determining, using a processor, a resource that is required by the Web page;

building a closure collection including the resource required by the Web page; and

writing a reference indicating the resource to the cache manifest.

2. The method of claim 1, wherein determining a resource that is required by the Web page comprises:

determining a target specified by the Web page as the resource.

3. The method of claim 1, further comprising:

determining that the resource is a static resource.

4. The method of claim 1, wherein each resource included within the closure collection is a static resource.

5. The method of claim 1, further comprising compressing at least a portion of the closure collection.

6. The method of claim 1, wherein the closure collection comprises at least a first resource and a second resource, the method further comprising:

consolidating the first resource and the second resource into a single, consolidated resource.

7. The method of claim 1, further comprising:

separating the Web application into a first component comprising the closure collection and the cache manifest and a second component, distinct from the first component, including at least a portion of the Web application not included in the first component.

8. The method of claim 7, further comprising:

deploying the first component to a first data processing system; and

deploying the second component to a second data processing system.

9. A method comprising:

deploying a first component of a Web application to a first data processing system, wherein the first component comprises a content cache specifying a list of resources and a closure collection comprising each resource in the list of the content cache; and

deploying a second component of the Web application to a second data processing system, wherein the second component comprises at least a portion of the Web application not included in the first component.