System and method for heterogeneous caching

• US 20030167377A1
• Filed: 01/10/2003
• Published: 09/04/2003
• Est. Priority Date: 01/18/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: White, Seth
• Granted Patent: US 6,978,278 B2
• Time in Patent Office: Days
• US Class Current: 711/118
• CPC Class Codes: G06F 12/084 with a shared cache
• CPC Class Codes: G06F 12/0875 with dedicated cache, e.g. instruction or stack
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

The caching of heterogeneous bean sets has been improved from requiring each bean to have its own cache instance to caching the beans in a single cache. The beans can be identified by generating a unique identifier that is a combination of the bean'"'"'s primary key and a self-reference identifier of the bean manager associated with that bean. The average size of a bean set associated with a bean manager can be specified such that the cache allocates memory for that set based on the average size. A callback interface can also be used to shift knowledge of a bean life cycle back to the bean manager.

This description is not intended to be a complete description of, or limit the scope of, the invention. Other features, aspects, and objects of the invention can be obtained from a review of the specification, the figures, and the claims.

Claims

1. A system for heterogeneous bean caching, comprising:

a bean having a primary key;

a cache capable of caching the bean;

a bean manager associated with the bean and the cache, the bean manager having a self-reference identifier; and

a key identifier for identifying the bean being cached in said cache, the key identifier comprising the primary key and the self-reference identifier.

2. A system according to claim 1, wherein:

the cache is further capable of caching additional beans associated with other bean managers.

3. A system according to claim 1, wherein:

the cache is further capable of managing the caching of the bean.

4. A system according to claim 1, wherein:

the bean has a life cycle, and said bean manager is further capable of managing the life cycle of said bean.

5. A system according to claim 1, wherein:

the bean manager is capable of creating the bean, storing the bean in the cache, loading the bean, and removing the bean from said cache.

6. A system according to claim 1, wherein:

the bean manager is further capable of making service requests on the cache.

7. A system according to claim 1, wherein:

the bean manager is further capable of providing the cache with the key identifier.

8. A system according to claim 1, wherein:

the key identifier comprises a Java class.

21. The system of claim 1 wherein:

the bean has a life-cycle and the cache has no knowledge of the lifecycle of said bean.

9. A method for heterogeneous bean caching, comprising:

generating a key identifier for a bean using the primary key of the bean and a self-reference identifier of a bean manager associated with the bean; and

using the key identifier to identify the bean in the cache.

10. A method according to claim 9, further comprising:

providing the key identifier to a cache for caching the bean.

11. A method according to claim 9, further comprising:

loading the bean into cache.

22. The method of claim 9 wherein the bean has a life-cycle, and further comprising:

using the bean manager to manage the life-cycle of the bean stored in the cache.

23. The method of claim 22 wherein:

the cache has no knowledge of the life-cycle of the bean.

12. A system for heterogeneous bean caching, comprising:

a first bean manager capable of being associated with first beans of a first size on average;

a second bean manager capable of being associated with second beans of a second size on average;

a cache associated with the first bean manager and the second bean manager and being capable of caching the first beans and the second beans, the cache allocating cache memory for storing the first beans based on the first size and allocating cache memory for storing the second beans based on the second size.

13. A system according to claim 12, further comprising:

an interface allowing the specification of the first size and the second size.

14. A system according to claim 12, further comprising:

a deployment descriptor allowing the specification of the first size and the second size.

24. The system of claim 12, wherein:

the first beans have life-cycles and the second beans have life-cycles, and wherein the cache has no knowledge of the life-cycles of the first beans and of the second beans.

25. The system of claim 12 wherein:

the first beans have life-cycles and the second beans have life-cycles, and the first bean manager manages the life-cycles of the first beans and the second bean manage manages the life-cycles of the second beans.

15. A method for heterogeneous bean caching, comprising:

specifying the average size of first beans to a cache;

specifying the average size of second beans to a cache; and

allowing the cache to allocate cache memory for the first beans based on the first size and to allocate cache memory for the second beans based on the second size.

16. A method according to claim 15, further comprising:

loading the first beans and the second beans into the cache.

20. The method of claim 15, further comprising:

using a bean manager to manage a life-cycle of the first beans stored in the cache.

26. The method of claim 15 wherein:

the first beans each have life-cycles and said cache has no knowledge of the life-cycles of the first beans.

17. A system for heterogeneous bean caching, comprising:

a bean adapted to hold a data instance;

a bean manager associated with the bean and capable of managing a life-cycle of the bean;

a cache associated with the bean manager and capable of caching the bean; and

a callback interface associated with the cache and allowing the cache to make callbacks on the bean manager related to the bean.

18. A system according to claim 17, wherein:

the cache is further adapted to send notification events related to the bean to the bean manager through the callback interface.

19. A system according to claim 17, wherein:

the cache contains no knowledge of the life-cycle of the bean.