Batching of invalidations and new values in a web cache with dynamic content

• US 20020116582A1
• Filed: 12/18/2000
• Published: 08/22/2002
• Est. Priority Date: 12/18/2000
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Copeland, George P., Flurry, Gregory A., Conner, Michael H.
• Application Number:
  US09/740,459
• Publication Number:
  US 20020116582A1
• Time in Patent Office: Days
• US Class Current: 711/133
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching

Abstract

A system and method are disclosed, according to which, the responsiveness of client/server-based distributed web applications operating in an object-oriented environment may be improved by batching invalidations of cache entries. Cache invalidations require updates of invalid cache entries from the database. Since database accesses are time-consuming, it is advantageous to combine several invalidations and execute them all at once (i.e.—to batch them). In an exemplary embodiment, cache entries may be identified or located on the basis of a unique ID. A list of IDs can be compiled by an application and consulted by a batch invalidation daemon, which uses the IDs therein to invalidate the desired entries. Alternatively, a time limit property of each cache entry can be examined by a time limit invalidation daemon, to invalidate entries that have “timed out”. Batching invalidations implies that invalid entries may remain in cache until the daemon wakes up. However, moderate latency in updating cached data is typically acceptable in e-business applications.

Claims

1. An system supporting distributed web applications between a client and a server, wherein the server is equipped with a cache, and the system comprises:

cache entries, comprising data, commands and server pages, which may be stored in the cache;

an invalidation instruction sequence, which invalidates selected cache entries in the cache; and

a batch update daemon, which awakes periodically, invoking the invalidation instruction sequence to invalidate multiple cache entries.

2. The system as recited in claim 1, further comprising a metadata property associated with each of the cache entries, wherein the metadata property associated with a particular cache entry contains zero or more data IDs, each of which is uniquely associated with data upon which the cache entry depends.

3. The system as recited in claim 2, wherein the batch update daemon may invoke the invalidation instruction sequence with a specific data ID, to invalidate cache entries for which the metadata property contains the data ID.

4. The system as recited in claim 2, wherein the metadata property associated with a particular cache entry also contains a cache ID, uniquely associated with the cache entry.

5. The system as recited in claim 4, wherein the batch update daemon may invoke the invalidation instruction sequence with a list of cache IDs, to invalidate cache entries for which the metadata property contains cache IDs included in the list.

6. The system as recited in claim 1, further comprising a group of caches, such that the batch update daemon may invoke the invalidation instruction sequence to invalidate selected cache entries in each cache within the group.

7. The system as recited in claim 4, wherein the metadata property also contains a time limit, which defines how long cache entries may remain in the cache.

8. The system as recited in claim 7, further comprising a time limit invalidation daemon, which detects entries whose time limit has expired and invalidates them.

9. The system as recited in claim 5, further comprising an invalidation table, which may be populated with data IDs or cache IDs by a database trigger, and using which, the batch update daemon selects entries to be invalidated.

10. The system further comprising a Java Virtual Machine (JVM), wherein the cache is associated with the JVM and the server pages stored therein are Java Server Pages (JSPs)

12. The method as recited in claim 10, further comprising attaching a distinct metadata property to each cache entry, wherein each metadata property contains zero or more data IDs, such that each data ID in the metadata property of a cache entry is uniquely associated with data upon which the cache entry depends.

11. A method for batching invalidation of cache entries in system supporting distributed web applications between a client and server, comprising:

specifying a plurality of cache entries for a batch of cache entries and;

periodically waking a batch invalidation daemon, which receives the identities of the specified cache entries and invokes an invalidation instruction sequence in the batch.

13. The method as recited in claim 11, wherein specifying a plurality of cache entries comprises listing the data ID associated with each of the plurality of cache entries.

14. The method as recited in claim 12, further comprising the batch update daemon invoking the invalidation instruction sequence with a specific data ID, to invalidate all cache entries for which the metadata property contains the data ID.

15. The method as recited in claim 13, wherein the metadata property also contains a cache ID, such that the cache ID in the metadata property of a particular cache entry is uniquely associated with the entry.

16. The method as recited in claim 14, wherein specifying a plurality of cache entries comprises listing the cache ID of each of the plurality of cache entries.

17. The method as recited in claim 15, further comprising the batch update daemon invoking the invalidation instruction sequence with a specific cache ID, to invalidate the cache entry for which the metadata property contains the data ID.

18. The method as recited in claim 16, wherein the metadata property of a cache entry also contains a time limit, which defines how long the entry may remain in the cache.

19. The method as recited in claim 17, further comprising a time limit invalidation daemon, which detects entries whose time limit has expired and invalidates them.

20. The method as recited in claim 18, further comprising creating an invalidation table, which may be populated with data IDs or cache IDs by a database trigger, and providing the table to the batch update daemon, to designate the entries to be invalidated.

21. A computer program product in a computer readable medium for batching invalidation of cache entries in a web application, comprising;

means for specifying a plurality of cache entries for a batch of cache entries; and

a batch invalidation daemon, which periodically wakes to receive the specified cache entries and invokes an invalidation instruction sequence on the batch.