Browse Prior Art Database

System and Method for Creating Custom Cache Keys using a Flexible and Extensible Cache

IP.com Disclosure Number: IPCOM000221947D
Publication Date: 2012-Sep-17
Document File: 3 page(s) / 63K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to increase flexibility when inserting elements into a cache. This article introduces the concept of a cache key provider, which provides a key used to look up an object in the cache. The advantage is that key creation is externalized to the key provider. The cache does not need to be aware of all the cache keys at runtime and it is not limited by the number of keys.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 01 of 3

System and Method for Creating Custom Cache Keys using a Flexible and Extensible Cache

The concept of a cache is a well-known mechanism for improving the performance of a system as well as implementing various algorithms. The problem addressed in this article is the lack of flexibility when inserting elements in a cache. The inflexibility of concern is the usage of hard-coded cache keys that cannot be modified when inserting those elements in the cache. Therefore, the keys used to look up a given element in the cache are restricted and cannot be easily extended.

A known solution, in an application server's custom cache keys, can be provided using
a custom login module. (Patent US20030236975. System and method for improved electronic security credentials.). The drawback of this known solution is that this cache key must be inserted into the Subject, which then requires a custom login module that involves a lot of configuration overhead. The known solution is expensive for customers because it requires customers to write a lot of code.

This article introduces the concept of a cache key provider, which provides a key used to look up an object in the cache. The advantage is that key creation is externalized to the key provider. The cache does not need to be aware of all the cache keys at runtime and it is not limited by the number of keys. For example, for the authentication cache, customers may want a way to determine a custom cache key. When a combination of the user ID and password is used as the key and this entry is added to the cache, all of the sessions are invalidated on the logout. To implement this custom cache key, no config...