System and method for heterogeneous caching

• US 20060004959A1
• Filed: 07/11/2005
• Published: 01/05/2006
• Est. Priority Date: 01/18/2002
• Status: Abandoned Application

• Current Assignee: BEA Systems Incorporated (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: White, Seth
• Application Number:
  US11/178,633
• Publication Number:
  US 20060004959A1
• 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, comprising:

a bean having a primary key;

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

a key identifier for identifying the bean, the key identifier comprising the primary key and the self-reference identifier.

2. The system of claim 1, further including a cache capable of caching the bean.

3. A system according to claim 2, wherein:

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

4. A system according to claim 2, wherein:

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

5. 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.

6. A system according to claim 2, 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.

7. A system according to claim 1, wherein:

the key identifier comprises a Java class.

8. 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, wherein the cache signals to bean manager to do operations related to the bean.

9. A system according to claim 8, further comprising a callback interface associated with the cache and allowing the cache to make callbacks on the bean manager related to the bean.

10. A system according to claim 9, wherein:

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

11. A system according to claim 8, wherein:

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

12. A system for heterogeneous bean caching, comprising:

a first set of beans;

a first bean manager associated with the first set of beans and capable of managing life-cycles of the first set of beans;

a second set of beans;

a second bean manager associated with the second set of beans and capable of managing life-cycles of the second set of beans; and

a cache associated with the first and second bean managers and capable of caching the first and second sets of beans.

13. The system of claim 12 wherein the first and second bean managers have different self-reference identifiers.

14. The system of claim 13 wherein each bean of the first and second set of beans have a primary key.

15. The system of claim 14, wherein a key identifier is used to identify a bean, the key identifier comprising a primary key of one of the beans and a self-reference identifier of one of the bean managers.

16. A system according to claim 15, wherein:

the key identifier comprises a Java class.

17. A system according to claim 12, wherein:

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

18. A system according to claim 12, wherein:

the bean managers are capable of creating a bean, storing a bean in the cache, loading the bean, and removing the bean from the cache.

19. A system according to claim 12, further comprising a callback interface associated with the cache and allowing the cache to make callbacks on the bean managers related to the bean.

20. A system according to claim 19, wherein:

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

21. A system according to claim 12, wherein:

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