Method and system for automatic cache management

• US 7,360,025 B1
• Filed: 12/11/2003
• Issued: 04/15/2008
• Est. Priority Date: 12/13/2002
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Vignette Corporation (Open Text Corporation)
• Inventors: Rajkumar, N. Isaac, O'Connell, Conleth, Scheevel, Mark R.
• Primary Examiner(s): Kim; Matthew
• Assistant Examiner(s): PATEL, HETUL B
• Application Number:
  US10/733,742
• Time in Patent Office: 1,587 Days
• Field of Search: 711/133, 711/159, 709218-219, 709/216, 709/231, 715/513, 707/201
• US Class Current: 711/133
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

Systems and methods which provide automatic management of cached content are disclosed. These systems and methods may provide a cache manager which is capable of updating content in a cache without receiving a request from a user. Content may be stored in a cache along with associated metadata. Based upon this metadata, the request which resulted in a particular piece of cached content may be regenerated. This regenerated request can be dynamically evaluated and content responsive generated. This newly generated content can be used to replace the previously cached content. Using these systems and methods content in a cache can be automatically managed and dynamically updated.

Claims

1. A method for updating a cache, comprising:

designating request metadata to be extracted from a request;

associating the request metadata and template metadata with content responsive to the request, wherein the request resulted in delivery of the content;

storing metadata in conjunction with the content responsive to the request in the cache, wherein the metadata includes the request metadata and the template metadata;

in response to a stimulus, regenerating the request from the metadata associated with the content stored in the cache;

passing the regenerated request to a server for new content;

receiving the new content, wherein the new content is generated based on the regenerated request; and

replacing the stored content with the new content in the cache.

2. The method of claim 1, further comprising receiving information on updated content.

3. The method of claim 2, wherein the request is regenerated in response to the information received.

4. The method of claim 3, wherein the metadata is template metadata or request metadata and the information received pertains to the template metadata or the request metadata.

5. The method of claim 4, wherein the information is received by a cache manager.

6. The method of claim 5, wherein the request is regenerated by the cache manager.

7. The method of claim 6, further comprising sending the information, wherein the information is sent by an application manager.

8. The method of claim 7, wherein the information is sent in response to a content change, metadata change, or template change.

9. The method of claim 8, wherein the information is sent via HTTP or JMS.

10. The method of claim 3, further comprising locating the previously stored content in the cache.

11. The method of claim 10, wherein locating previously stored content comprises comparing the received information with the template metadata associated with the previously stored content.

12. The method of claim 10, wherein locating previously stored content comprises comparing the received information with the request metadata associated with the previously stored content.

13. The method of claim 1, wherein regenerating the request is not based on a user request.

14. The method of claim 13, wherein regenerating the request is based on a timer.

15. The method of claim 14, wherein the timer is associated with the previously stored data.

16. A system for updating a cache, comprising

a cache manager operable to

allow designation of request metadata to be extracted from a request;

associate the request metadata and template metadata with content responsive to the request, wherein the request resulted in delivery of the content;

store metadata in conjunction with the content responsive to the request in the cache, wherein the metadata includes the request metadata and the template metadata;

in response to a stimulus, regenerate the request from the metadata associated with the content previously stored in the cache;

pass the regenerated request to a server for new content;

receive the new content, wherein the new content is generated based on the regenerated request; and

replace the stored content with the new content in the cache.

17. The system of claim 16, wherein the cache manager is further operable to receive information on updated content.

18. The system of claim 17, wherein the request is regenerated in response to the information received.

19. The system of claim 18, wherein the metadata is template metadata or request metadata and the information received pertains to the template metadata or the request metadata.

20. The system of claim 19, further comprising an application manager operable to send the information.

21. The system of claim 20, wherein the information is sent in response to a content change, metadata change, or template change.

22. The system of claim 21, wherein the information is sent via HTTP or JMS.

23. The system of claim 18, further comprising locating the previously stored content in the cache.

24. The system of claim 23, wherein locating previously stored content comprises comparing the received information with the template metadata associated with the previously stored content.

25. The system of claim 23, wherein locating previously stored content comprises comparing the received information with the request metadata associated with the previously stored content.

26. The system of claim 16, wherein regenerating the request is not based on a user request.

27. The system of claim 26, wherein regenerating the request is based on a timer.

28. The system of claim 27, wherein the timer is associated with the previously stored data.

29. A software system for updating a cache, comprising machine or computer readable media containing instructions translatable for:

allowing designation of request metadata to be extracted from a request;

associating the request metadata and template metadata with content responsive to the request, wherein the request resulted in delivery of the content;

storing metadata in conjunction with the content responsive to the request in the cache, wherein the metadata includes the request metadata and the template metadata;

in response to a stimulus, regenerating the request from the metadata associated with the content stored in the cache;

passing the regenerated request to a server for new content;

receiving the new content, wherein the new content is generated based on the regenerated request; and

replacing the stored content with the new content in the cache.

30. The software system of claim 29, further comprising instructions translatable for receiving information on updated content.

31. The software system of claim 30, wherein the request is regenerated in response to the information received.

32. The software system of claim 31, wherein the metadata is template metadata or request metadata and the information received pertains to the template metadata or the request metadata.

33. The software system of claim 32, wherein the information is received by a cache manager.

34. The software system of claim 33, wherein the request is regenerated by the cache manager.

35. The software system of claim 34, further comprising instructions translatable for sending the information, wherein the information is sent by an application manager.

36. The software system of claim 35, wherein the information is sent in response to a content change, metadata change, or template change.

37. The software system of claim 36, wherein the information is sent via HTTP or JMS.

38. The software system of claim 31, further comprising instructions translatable for locating the previously stored content in the cache.

39. The software system of claim 38, wherein locating previously stored content comprises comparing the received information with the template metadata associated with the previously stored content.

40. The software system of claim 38, wherein locating previously stored content comprises comparing the received information with the request metadata associated with the previously stored content.

41. The software system of claim 29, wherein regenerating the request is not based on a user request.

42. The software system of claim 41, wherein regenerating the request is based on a timer.

43. The software system of claim 42, wherein the timer is associated with the previously stored data.