Method and system for fragment linking and fragment caching

• US 7,730,154 B2
• Filed: 12/19/2001
• Issued: 06/01/2010
• Est. Priority Date: 12/19/2001
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Challenegr, James R. H., Iyengar, Arun K., Copeland, George P., Agarwalla, Rajesh S., Meduri, Subbarao, Linehan, Mark H.
• Primary Examiner(s): WANG, LIANG CHE A
• Application Number:
  US10/034,772
• Publication Number:
  US 20030187935A1
• Time in Patent Office: 3,086 Days
• Field of Search: 709/217, 709/236, 709/203, 709/230, 711/3, 711111-118, 717/148
• US Class Current: 709/217
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method, a system, an apparatus, and a computer program product are presented for fragment caching. After a message is received at a computing device that contains a cache management unit, a fragment in the message body of the message is cached. Subsequent requests for the fragment at the cache management unit result in a cache hit. The cache management unit operates equivalently in support of fragment caching operations without regard to whether the computing device acts as a client, a server, or a hub located throughout the network; in other words, the fragment caching technique is uniform throughout a network. Cache ID rules accompany a fragment from an origin server; the cache ID rules describe a method for forming a unique cache ID for the fragment such that dynamic content can be cached away from an origin server.

Claims

1. A method for processing objects at a data processing system in a network, the method comprising processing logic used for:

receiving a message at a computing device;

determining that a message header in the message indicates that the message relates to a fragment and that the fragment is cacheable, wherein the message header comprises no-cache directive data for not caching the fragment for non-fragment-supporting cache management units and caching directive data for caching the fragment for fragment-supporting cache management units;

determining whether a cache management unit is a non-fragment-supporting cache management unit or a fragment-supporting cache management unit;

processing the no-cache directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit;

processing the caching directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit;

retrieving a set of dependency identifiers from the message, wherein a dependency identifier is generated by a server that originated the fragment;

storing the set of dependency identifiers in association with a source identifier for the fragment;

receiving an invalidation request message;

retrieving a dependency identifier from the invalidation request message;

determining a set of fragments that are associated with the dependency identifier; and

purging the set of fragments from the cache in response to determining the set of fragments that are associated with the dependency identifier.

2. The method of claim 1 further comprising:

storing a fragment from the message in a cache maintained by a fragment-supporting cache management unit within the computing device, wherein the fragment-supporting cache management unit operates equivalently in support of fragment caching operations whether the computing device acts as a client, a server, or a hub located throughout the network.

3. The method of claim 1 further comprising:

determining that a message header in the message indicates that a message body portion of the message is a fragment.

4. The method of claim 1 wherein the message header comprises an HTTP Cache-Control header.

5. The method of claim 1 further comprising:

retrieving a set of fragment caching rules from the message, wherein a fragment caching rule determines a manner for generating a cache identifier for the fragment; and

generating a cache identifier for the fragment in accordance with a fragment caching rule.

6. The method of claim 5 further comprising:

uniquely identifying the fragment using the cache identifier.

7. The method of claim 5 further comprising:

performing the storing operation using the generated cache identifier for the fragment.

8. The method of claim 5 further comprising:

obtaining at least a path portion of a URI (Uniform Resource Identifier) associated with the fragment in order to form a base cache identifier; and

applying a fragment caching rule to the base cache identifier to form a cache identifier for the fragment, wherein a fragment caching rule comprises a set of query parameter names and/or cookie names that are used to obtain name-value pairs that are appended to the base cache identifier.

9. An apparatus for processing objects at a data processing system in a network, the apparatus comprising:

means for receiving a message at a computing device;

means for determining that a message header in the message indicates that the message relates to a fragment and that the fragment is cacheable, wherein the message header comprises no-cache directive data for not caching the fragment for non-fragment-supporting cache management units and caching directive data for caching the fragment for fragment-supporting cache management units;

means for determining whether a cache management unit is a non-fragment-supporting cache management unit or a fragment-supporting cache management unit;

means for processing the no-cache directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit;

means for processing the caching directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit;

means for retrieving a set of dependency identifiers from the message, wherein a dependency identifier is generated by a server that originated the fragment;

means for storing the set of dependency identifiers in association with a source identifier for the fragment;

means for receiving an invalidation request message;

means for retrieving a dependency identifier from the invalidation request message;

means for determining a set of fragments that are associated with the dependency identifier; and

means for purging the set of fragments from the cache in response to determining the set of fragments that are associated with the dependency identifier.

10. The apparatus of claim 9 further comprising:

means for storing a fragment from the message in a cache maintained by a fragment-supporting cache management unit within the computing device, wherein the fragment-supporting cache management unit operates equivalently in support of fragment caching operations whether the computing device acts as a client, a sewer, or a hub located throughout the network.

11. The apparatus of claim 9 further comprising:

means for determining that a message header in the message indicates that a message body portion of the message is a fragment.

12. The apparatus of claim 9 wherein the message header comprises an HTTP Cache-Control header.

13. The apparatus of claim 9 further comprising:

means for retrieving a set of fragment caching rules from the message, wherein a fragment caching rule determines a manner for generating a cache identifier for the fragment; and

means for generating a cache identifier for the fragment in accordance with a fragment caching rule.

14. The apparatus of claim 13 further comprising:

means for uniquely identifying the fragment using the cache identifier.

15. The apparatus of claim 13 further comprising:

means for performing the storing operation using the generated cache identifier for the fragment.

16. The apparatus of claim 13 further comprising:

means for obtaining at least a path portion of a URI (Uniform Resource Identifier) associated with the fragment in order to form a base cache identifier; and

means for applying a fragment caching rule to the base cache identifier to form a cache identifier for the fragment, wherein a fragment caching rule comprises a set of query parameter names and/or cookie names that are used to obtain name-value pairs that are appended to the base cache identifier.

17. A computer program product in a computer readable storage medium for use in a data processing system in a network for processing objects, the computer program product comprising:

instructions for receiving a message at a computing device; and

instructions for determining that a message header in the message indicates that the message relates to a fragment and that the fragment is cacheable, wherein the message header comprises no-cache directive data for not caching the fragment for non-fragment-supporting cache management units and caching directive data for caching the fragment for fragment-supporting cache management units;

instructions for determining whether a cache management unit is a non-fragment-supporting cache management unit or a fragment-supporting cache management unit;

instructions for processing the no-cache directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit; and

instructions for processing the caching directive data to generate a no-cache instruction to a non-fragment-supporting cache management unit;

instructions for retrieving a set of dependency identifiers from the message, wherein a dependency identifier is generated by a server that originated the fragment;

instructions for storing the set of dependency identifiers in association with a source identifier for the fragment;

instructions for receiving an invalidation request message;

instructions for retrieving a dependency identifier from the invalidation request message;

instructions for determining a set of fragments that are associated with the dependency identifier; and

instructions for purging the set of fragments from the cache in response to determining the set of fragments that are associated with the dependency identifier.

18. The computer program product of claim 17 further comprising:

instructions for storing a fragment from the message in a cache maintained by a fragment-supporting cache management unit within the computing device, wherein the fragment-supporting cache management unit operates equivalently in support of fragment caching operations whether the computing device acts as a client, a server, or a hub located throughout the network.

19. The computer program product of claim 17 further comprising:

instructions for determining that a message header in the message indicates that a message body portion of the message is a fragment.

20. The computer program product of claim 17 wherein the message header comprises an HTTP Cache-Control header.

21. The computer program product of claim 17 further comprising:

instructions for retrieving a set of fragment caching rules from the message, wherein a fragment caching rule determines a manner for generating a cache identifier for the fragment; and

instructions for generating a cache identifier for the fragment in accordance with a fragment caching rule.

22. The computer program product of claim 21 further comprising:

instructions for uniquely identifying the fragment using the cache identifier.

23. The computer program product of claim 21 further comprising:

instructions for performing the storing operation using the generated cache identifier for the fragment.

24. The computer program product of claim 21 further comprising:

instructions for obtaining at least a path portion of a URI (Uniform Resource Identifier) associated with the fragment in order to form a base cache identifier; and

instructions for applying a fragment caching rule to the base cache identifier to form a cache identifier for the fragment, wherein a fragment caching rule comprises a set of query parameter names and/or cookie names that are used to obtain name-value pairs that are appended to the base cache identifier.