Automatic cache synchronization

• US 6,233,606 B1
• Filed: 12/01/1998
• Issued: 05/15/2001
• Est. Priority Date: 12/01/1998
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Dujari, Rajeev
• Primary Examiner(s): Coulter, Kenneth R.
• Application Number:
  US09/203,303
• Time in Patent Office: 896 Days
• Field of Search: 709/213
• US Class Current: 709/213
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A method and system for reducing the number of conditional requests for network content to a server by maintaining state for selected URIs in a local cache indicative of a confidence level that the files are unchanged. When a request for content is received that corresponds to such a URI in the cache, a synchronization time is determined based on a confidence level for that URI. If the synchronization time is achieved, a conditional request is sent to the server, otherwise the URI data is returned from the cache to respond to the request. Synchronization intervals for such files may be increased as the likelihood that the item is unmodified increases. URIs may need to be of a certain content type and required to pass a confidence test before being selected for automatic synchronization.

Claims

1. In a computer system, a method for synchronizing content with content stored in a cache, comprising the steps of, receiving a request for content, at least part of the requested content corresponding to data in the cache, determining a synchronization time for the content based on a confidence level therefor, and if a current time is before the synchronization time, returning data from the cache in response to the request.

2. The method of claim 1 wherein the step of determining a synchronization time includes the steps of, performing a confidence test to test the stability of the content, and setting an automatic synchronization mode for the content if the confidence test indicates that the content is relatively stable.

3. The method of claim 2 wherein the confidence test includes a test of the time that the content has been in the cache without having changed.

4. The method of claim 3 further comprising the step of marking the content as volatile if the content changes before having been in the cache for a predetermined time.

5. The method of claim 2 wherein the confidence test includes a test of the number of times that the content has been checked without having changed.

6. The method of claim 5 further comprising the step of marking the content as volatile if the content changes before having been checked a predetermined number of times.

7. The method of claim 2 wherein the confidence test includes a test of the time that the content has been in the cache without having changed, and a test of the number of times that the content has been checked without having changed.

8. The method of claim 7 further comprising the step of marking the content as volatile if either the content changes before having been in the cache for a predetermined time or if the content changes before having been checked a predetermined number of times.

9. The method of claim 1 wherein the step of determining a synchronization time for the content based on the confidence level includes the step of checking to determine if the content is marked as volatile.

10. The method of claim 9 wherein if the content is determined to be volatile, the synchronization time is achieved.

11. The method of claim 1 wherein the step of determining a synchronization time for the content based on the confidence level includes the step of checking to determine if the content corresponds to a specific type.

12. The method of claim 11 wherein if the content does not correspond to a specific type, the synchronization time is achieved.

13. The method of claim 1 wherein if the content does not have a minimum confidence level, the synchronization time is achieved.

14. The method of claim 1 wherein the content comprises network content corresponding to a Uniform Resource Identifier (URI), and wherein if the synchronization time is achieved, performing the step of sending a conditional request to a server for the content, and further comprising the step of gathering confidence information based on a response of the conditional request sent to the server.

15. The method of claim 14 wherein the confidence information is used to modify the confidence level for the URI.

16. The method of claim 1 wherein if the synchronization time is achieved, making a request for current content, and further comprising the steps of, receiving the current content, testing if the current content is modified relative to the cached content, and if not modified, increasing the confidence level for the cached content.

17. In a computer system, a method for synchronizing network content with content stored in a cache, comprising the steps of, receiving a request for content, at least part of the requested content corresponding to data in the cache, determining a synchronization time for a URI based on a confidence level for the URI, and if the synchronization time is achieved, sending a conditional request to a server for the content, and if the synchronization time is not achieved, returning data from the cache in response to the request.

18. The method of claim 17 wherein the step of determining a synchronization time for the URI includes the steps of performing a confidence test to test the stability of the URI and setting an automatic synchronization mode for the URI if the confidence test indicates that the URI is relatively stable.

19. The method of claim 18 wherein the confidence test includes a test of the time that the content has been in the cache without having changed.

20. The method of claim 19 further comprising the step of marking a URI as volatile if the content changes before having been in the cache for a predetermined time.

21. The method of claim 18 wherein the confidence test includes a test of the number of times that the URI has been checked without having changed.

22. The method of claim 21 further comprising the step of marking a URI as volatile if the content changes before having been checked a predetermined number of times.

23. The method of claim 18 wherein the confidence test includes a test of the time that the content has been in the cache without having changed, and a test of the number of times that the URI has been checked without having changed.

24. The method of claim 23 further comprising the step of marking a URI as volatile if either the content changes before having been in the cache for a predetermined time or if the content changes before having been checked a predetermined number of times.

25. The method of claim 17 wherein the step of determining a synchronization time for the URI based on a confidence level for the URI includes the step of checking to determine if the URI is marked as volatile.

26. The method of claim 25 wherein if the URI is determined to be volatile, the synchronization time is achieved.

27. The method of claim 17 wherein the step of determining a synchronization time for the URI based on a confidence level for the URI includes the step of checking to determine if the content corresponds to a specific type.

28. The method of claim 27 wherein if the content does not correspond to a specific type, the synchronization time is achieved.

29. The method of claim 17 wherein if the URI does not have a minimum confidence level, the synchronization time is achieved.

30. The method of claim 17 further comprising the step of gathering confidence information based on a response of each conditional request sent to the server.

31. The method of claim 30 wherein the confidence information is used to modify the confidence level for a URI.

32. The method of claim 17 further comprising the steps of testing if a content has been modified after sending a conditional request to the server, and if not modified, increasing the confidence level for that URI.

33. The method of claim 18 further comprising the steps of, receiving another request for content corresponding to the URI, determining if the URI is in the automatic synchronization mode, and if so:

determining a time for synchronizing the URI, and, if the time for synchronizing is achieved, sending

another conditional request to the server, and if the time for synchronizing is not achieved,

returning content data from the cache.

34. The method of claim 33 wherein if the URI is not in an automatic synchronization mode, sending another conditional request to the server, and further comprising the step of gathering information for the URI including information on whether the conditional request indicates the content has changed.

35. The method of claim 34 further comprising the step of determining whether to enter the URI into the automatic synchronization mode based on the information.

36. In a computer system, a system for synchronizing network content with content stored in a cache, comprising, a network interface for receiving a request for content, a cache manager component for determining that at least part of the requested content corresponds to data in the cache, a storage for maintaining a confidence level for the URI, and an automatic synchronization mechanism for accessing the storage to determine a synchronization time for the URI based on the confidence level therefor, the interface responding to the request by sending a conditional request to a server for the content if the synchronization time is achieved, and returning data from the cache if the synchronization time is not achieved.

37. The system of claim 36 wherein the automatic synchronization mechanism further performs a confidence test to test the stability of the URI, and sets an automatic synchronization mode for the URI if the confidence test indicates that the URI content is relatively stable.

38. The system of claim 37 wherein the confidence test includes a test of the time that the URI content has been in the cache without having changed.

39. The system of claim 37 wherein the confidence test includes a test of the number of times that the URI has been checked without having changed.

40. The system of claim 36 wherein the automatic synchronization mechanism further gathers confidence information based on a response of each conditional request sent to the server, and stores the confidence information in the storage for that URI.

41. The system of claim 40 wherein if URI content has not been modified after sending a conditional request to the server, the automatic synchronization mechanism increases the confidence level for that URI.