Cache invalidation technique with spurious resource change indications

• US 6,912,562 B1
• Filed: 01/13/2003
• Issued: 06/28/2005
• Est. Priority Date: 12/04/2002
• Status: Expired due to Term

• Current Assignee: AT&T Corporation (AT&T, Inc.)
• Original Assignee: AT&T Corporation (AT&T, Inc.)
• Inventors: Krishnamurthy, Balachander, Rabinovich, Michael
• Primary Examiner(s): Bragdon, Reginald G.
• Application Number:
  US10/339,687
• Time in Patent Office: 897 Days
• Field of Search: 709/203, 709/229, 711/133, 711/144
• US Class Current: 709/203
• CPC Class Codes: G06F 12/0891 using clearing, invalidating or resetting means
• 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 Web server maintains, for one or more resources, a respective list of clients who requested that resource. The server takes on the responsibility of notifying all of those clients on when the resource in question changes, thereby letting them know that if the resource is again asked for by a user, an updated copy will have to be requested from the origin server. The server thereupon purges the client list, and then begins rebuilding it as subsequent requests come in for the resource in question. Invalidation messages are sent to selected “victim” clients on the client list, independent of whether the resource in question has changed, when the list meets a predetermined criterion, such as becoming too large. The victim clients may include clients who access the server less frequently than others, clients who have accessed the server in the more distant past than other clients, i.e., using a first-in-first methodology, or clients who have not subscribed to a service that keeps them from being victim clients. Review of a client list to determine whether it meets the selected criterion can be invoked every time a client gets added to a client list or on a scheduled basis.

Claims

1. A server invalidation method for use by a server that maintains a client list for a resource, the method comprising transmitting an invalidation message for said resource to at least one of the clients on said client list, said invalidation message being transmitted even though said resource did not change subsequent to said resource having been served to said client.

2. The invention of claim 1 wherein said invalidation message is a spurious indication that said resource has changed.

3. The invention of claim 2 further comprising removing said at least one of said clients from said client list.

4. The invention of claim 3 wherein said transmitting is performed as a function of a particular characteristic of said client list.

5. The invention of claim 4 wherein said particular characteristic is the number of clients on said client list.

6. The invention of claim 1 further comprising identifying, as said at least one of said clients, a client on said client list which, over some period of time, has accessed said server less frequently than at least one other client on said client list.

7. The invention of claim 1 wherein said at least one of said clients is a client identified on the basis of information about that client.

8. The invention of claim 7 wherein said information about the client is the nature of the client'"'"'s access behavior.

9. The invention of claim 7 wherein said information about the client is the quality of the client'"'"'s connectivity with said server.

10. The invention of claim 1 further comprising identifying, as said at least one of said clients, a client on said client list which last accessed said server at a more distant time in the past than at least one other client on said client list.

11. The invention of claim 1 further comprising:

maintaining a list of clients that are not to receive said invalidation message,

and wherein said at least one of said clients is a client not on that list.

12. A method for use by a server that serves at least one resource, the method comprising:

maintaining a list of clients to whom a particular version of a resource was sent by said server, and

transmitting to at least one of said clients on said client list an invalidation message indicative of the fact that a newer version of said resource is available to be served by said server, said invalidation message being transmitted even though said server is still responding to requests for said resource by serving said particular version of said resource.

13. The invention of claim 12 further comprising removing said at least one of said clients from said client list.

14. The invention of claim 13 wherein said transmitting is performed in response to a determination made during a review of said client list that the number of clients on said client list exceeds a specified limit.

15. The invention of claim 14 wherein said client list review is undertaken in response to a client being added to said client list.

16. The invention of claim 14 wherein said client list review is undertaken on a scheduled basis.

17. The invention of claim 16 wherein said client list review is undertaken more frequently for a client list whose associated resource is accessed more frequently than for client lists associated with other resources served by said server.

18. The invention of claim 14 wherein said server performs said client list review at variable time intervals that are dependent upon whether said client list was found to exceed said specified limit for any given client list review.

19. The invention of claim 14 further comprising, in response to a newer version of said resource being made available to be served on said server,

transmitting said invalidation message to all of the clients on said client list, and

removing all of the clients from said client list.

20. A method for use by a server comprising:

maintaining client lists each associated with a respective one of a plurality of resources,

responding to a request from a client for an individual one of said resources by a) causing the requested resource to be served to said client, b) placing said client on a particular client list, said particular client list being the list associated with the requested resource, and c) causing said client to thereafter utilize a cached copy of the requested resource without fist determining from said server whether said requested resource had changed,

responsive to there being a change in said resource a) sending an invalidation message to at least ones of the clients on said particular client list, said invalidation message being indicative of the fact that the resource has changed since it was served to said at least ones of said clients and b) removing said at least ones of said clients from said particular client list, and

sending an invalidation message to at least one of the clients on said particular client list in response to said particular client list meeting a predetermined criterion.

21. The invention of claim 20 wherein said causing said client to thereafter utilize a cached copy of the requested resource comprises communicating an expiration time for said resource to said client.

22. The invention of claim 20 wherein said predetermined criterion is that the number of clients on said client list exceeds a predefined limit.

23. The invention of claim 22 further comprising identifying, as said at least one of said clients, a client on said client list which, over some period of time, has accessed said server less frequently than at least one other client on said client list.

24. The invention of claim 22 further comprising identifying, as said at least one of said clients, a client on said client list which last accessed said server at a more distant time in the past than at least one other client on said client list.

25. The invention of claim 22 wherein said at least one of said clients is a client identified on the basis of information about that client.

26. The invention of claim 25 wherein said information about the client is the nature of the client'"'"'s access behavior.

27. The invention of claim 25 wherein said information about the client is the quality of the client'"'"'s connectivity with said server.

28. The invention of claim 22 further comprising:

maintaining a list of clients that are not to receive said invalidation message,

and wherein said at least one of said clients is a client not on that list.

29. The invention of claim 22 wherein it is determined whether said predetermined criterion is met during a client list review undertaken in response to a client being added to said client list.

30. The invention of claim 22 wherein it is determined whether said predetermined criterion is met during a client list review undertaken on a scheduled basis.

31. The invention of claim 30 wherein a frequency with which said client list review is undertaken is a function of a frequency with which the associated resource is accessed.

32. The invention of claim 30 wherein a frequency with which said client list review is undertaken is a function of a rate of change of the associated resource.

33. The invention of claim 30 wherein said client list review is undertaken at variable time intervals that are dependent upon whether said client list was found to exceed said specified limit for any given client list review.

34. An article of manufacture, comprising a machine accessible medium having instructions encoded thereon for enabling a server that serves at least one resource to perform the operations of:

maintaining a list of clients to whom a particular version of a resource was sent by said server, and

transmitting to at least one of said clients on said client list an invalidation message indicative of the fact that a newer version of said resource is available to be served from said server, said invalidation message being transmitted even though said server is still responding to requests from said particular resource by serving said particular version of said resource.

35. The invention of claim 34 wherein said instructions further enable said server to perform the operation of removing said at least one of said clients from said client list.

36. The invention of claim 35 wherein said transmitting is performed in response to a determination that the number of clients on said client list exceeds a specified limit.

37. The invention of claim 36 wherein said instructions further enable said server, in response to a newer version of said resource being made available to be served from said server, to perform the further operations of:

transmitting said invalidation message to all of the clients on said client list, and

removing all of the clients from said client list.

38. A server adapted to:

maintain a client list associated with each of a plurality of resources,

respond to a request from a client for an individual one of said resources by a) causing the requested resource to be served to said client and b) placing said client on a particular client list, said particular client list being the list associated with the requested resource,

in response to there being a change in said resource a) send an invalidation message to at least ones of the clients on said particular client list, said invalidation message being indicative of the fact that the resource has changed since it was served to said at least ones of said clients and b) remove said at least ones of said clients from said particular client list, and

send an invalidation message to at least one of the clients on said particular client list in response to said particular client list meeting a predetermined criterion.

39. The invention of claim 38 wherein said predetermined criterion is that the number of clients on said client list exceeds a predefined limit.

40. The invention of claim 38 wherein said server is further adapted to send to said client, when said resource is served to said client, information indicating that said resource will be valid for at least a specified amount of time.

41. The invention of claim 38 wherein said server is further adapted to identify, as said at least one of said clients, a client on said client list which, over some period of time, has accessed said server less frequently than at least one other client on said client list.

42. The invention of claim 38 wherein said server is further adapted to identify, as said at least one of said clients, a client on said client list which last accessed said server at a more distant time in the past than at least one other client on said client list.

43. The invention of claim 38 wherein said server is further adapted to

maintain a list of clients that are not to receive said invalidation message,

and wherein said at least one of said clients is a client not on that list.

44. The invention of claim 38 wherein it is determined whether said predetermined criterion is met during a client list review undertaken in response to a client being added to said client list.

45. The invention of claim 38 wherein it is determined whether said predetermined criterion is met during a client list review undertaken on a scheduled basis.

46. The invention of claim 45 wherein said client list review is undertaken more frequently for a client list whose associated resource is accessed more frequently than for client lists associated with other resources served by said server.

47. The invention of claim 45 wherein said client list review is undertaken at variable time intervals that are dependent upon whether said client list was found to exceed said specified limit for any given client list review.