Method and apparatus for cache management of distributed objects

• US 8,195,610 B1
• Filed: 05/08/2007
• Issued: 06/05/2012
• Est. Priority Date: 05/08/2007
• Status: Expired due to Fees

• Current Assignee: IdeaBlade, Inc.
• Original Assignee: IdeaBlade, Inc.
• Inventors: Traband, Jonathan Jay, Bell, Ward Raymond, Wang, Albert Szu-chi
• Primary Examiner(s): Pulliam, Christyann
• Application Number:
  US11/745,933
• Time in Patent Office: 1,855 Days
• Field of Search: 707/616, 707/638
• US Class Current: 707/638
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 16/24552 Database cache management
• CPC Class Codes: G06F 16/278 Data partitioning, e.g. horizontal or vertical partitioning

Abstract

A method and apparatus for cache management of distributed objects have been disclosed. A query strategy, based on a fetch strategy and a merge strategy, may be used to query a database and reconcile data in a local cache. In one approach, a merge action depends upon whether an entity was added, deleted, or changed relative to the original version of the entity as it was last fetched.

Claims

1. A computer implemented method comprising:

(a) determining when a cached entity has a corresponding existing entity in a datasource, and

when said cached entity has said corresponding existing entity in said datasource then;

(b) determining when a preserve changes to said cached entity merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource, and

when said preserve change to said cached entity merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource then;

(c) determining when said cached entity has a current version of said cached entity having a status of unmodified, and

(c1) when said cached entity has said current version of said cached entity having said status of unmodified then;

(c1a) replacing said current version of said cached entity with data from said corresponding existing entity in said datasource, replacing an original version of said cached entity with said data from said corresponding existing entity in said datasource,

(c2) when said cached entity has said current version of said cached entity having said status of unmodified then;

(c2a) leaving unchanged said status of said current version of said cached entity;

and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

2. The method of claim 1 further comprising:

(d) determining when said cached entity has a current version of said cached entity having a status of other than unmodified, and

(d1) when said cached entity has said current version of said cached entity having said status of other than unmodified then;

(d1a) leaving unchanged said current version of said cached entity, leaving unchanged an original version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

3. The computer implemented method of claim 2 further comprising:

(d2) when said cached entity has said current version of said cached entity having said status of other than unmodified then;

(d2a) leaving unchanged said status of said current version of said cached entity.

4. The method of claim 2 wherein said cached entity is not obsolete after said leaving unchanged said current version of said cached entity and leaving unchanged said original version of said cached entity.

5. A computer implemented method comprising:

determining when a cached entity has a corresponding existing entity in a datasource, and

when said cached entity has said corresponding existing entity in said datasource then;

determining when an overwrite changes to said cached entity merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource, and

when said overwrite changes to said cached entity merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource then;

replacing a current version of said cached entity with data from said corresponding existing entity in said datasource,

replacing an original version of said cached entity with said data from said corresponding existing entity in said datasource,

changing a status to unmodified for a current version of said cached entity;

wherein said cached entity is not obsolete after said replacing said current version of said cached entity with said data from said corresponding existing entity in said datasource and said replacing said original version of said cached entity with said data from said corresponding existing entity in said datasource and said changing said status to unmodified for said current version of said cached entity;

and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

6. A computer implemented method comprising:

determining when a cached entity has a corresponding existing entity in a datasource, and

when said cached entity has said corresponding existing entity in said datasource then;

determining when a preserve changes unless an original version of said cached entity is obsolete merge strategy is requested for said cached entity with said corresponding existing entity in said datasource, and when said preserve changes unless said original version of said cached entity is obsolete merge strategy is requested for said cached entity with said corresponding existing entity in said datasource then;

determining when said cached entity is not obsolete, and

when said cached entity is not obsolete then;

determining when said cached entity has a current version of said cached entity having a status of unmodified, and

when said cached entity has said current version of said cached entity having said status of unmodified then;

replacing a current version of said cached entity with data from said corresponding existing entity in said datasource, replacing an original version of said cached entity with said data from said corresponding existing entity in said datasource, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

when said cached entity has said current version of said cached entity having said status of other than unmodified then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity is obsolete, and

when said cached entity is obsolete then;

replacing a current version of said cached entity with data from said corresponding existing entity in said datasource, replacing an original version of said cached entity with said data from said corresponding existing entity in said datasource, changing said status to unmodified for said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

7. The method of claim 6 wherein said cached entity is not obsolete after said replacing said current version of said cached entity with data from said corresponding existing entity in said datasource.

8. A computer implemented method comprising:

determining when a cached entity has a corresponding existing entity in a datasource, and

when said cached entity has said corresponding existing entity in said datasource then;

determining when a preserve changes and update an original version of said cached entity merge strategy is requested for said cached entity with said corresponding existing entity in said datasource, and

when said preserve changes and update said original version of said cached entity merge strategy is requested for said cached entity with said corresponding existing entity in said datasource then;

determining when said cached entity has a current version of said cached entity having a status of unmodified, and

when said cached entity has said current version of said cached entity having said status of unmodified then;

 

replacing said current version of said cached entity with data from said corresponding existing entity in said datasource,

 

replacing an original version of said cached entity with said data from said corresponding existing entity it in said datasource, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of added, and

 

when said cached entity has said current version of said cached entity having said status of added then;

 

leaving unchanged said current version of said cached entity, replacing an original version of said cached entity with data from said corresponding existing entity in said datasource, and changing said status to modified for said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

 

determining when said cached entity has a current version of said cached entity having a status of other than added and having a status of other than unmodified, and

 

when said cached entity has said current version of said cached entity having said status of other than added and having said status of other than unmodified then;

 

leaving unchanged said current version of said cached entity, replacing an original version of said cached entity with data from said corresponding existing entity in said datasource, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

9. The method of claim 8 wherein said cached entity is not obsolete after said replacing said original version of said cached entity with data from said corresponding existing entity in said datasource.

10. A computer implemented method comprising:

determining when a cached entity has a corresponding existing entity in a datasource, and

when said cached entity has said corresponding existing entity in said datasource then;

determining when a preserve said existing entity in said datasource when said existing entity in said datasource is found in a cache merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource, and

when a preserve said existing entity in said datasource when said existing entity in said datasource is found in said cache merge strategy is requested for said cached entity merging with said corresponding existing entity in said datasource then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged a status of said current version of said cached entity, and

wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

11. A computer implemented method comprising:

determining when a cached entity does not exist in a datasource, and

when said cached entity does not exist in said datasource then;

determining when a preserve changes to said cached entity merge strategy is requested for said cached entity merging with said datasource, and when said preserve changes to said cached entity merge strategy is requested for said cached entity merging with said datasource then;

determining when said cached entity has a current version of said cached entity having a status of unmodified, and

when said cached entity has said current version of said cached entity having said status of unmodified then;

removing said cached entity, and wherein a remove status related to said removing of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of other than unmodified, and

when said cached entity has said current version of said cached entity having said status of other than unmodified then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

12. A computer implemented method comprising:

determining when a cached entity does not exist in a datasource, and

when said cached entity does not exist in said datasource then;

determining when an overwrite changes to said cached entity merge strategy is requested for said cached entity merging with said datasource, and when said overwrite changes to said cached entity merge strategy is requested for said cached entity merging with said datasource then;

determining when said cached entity has a current version of said cached entity having a status of added, and

when said cached entity has said current version of said cached entity having said status of added then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of other than added, and

when said cached entity has said current version of said cached entity having said status of other than added then;

removing said cached entity, and wherein a remove status related to said of said cached entity is stored in hardware on said computer and is displayed for a user.

13. A computer implemented method comprising:

determining when a cached entity does not exist in a datasource, and

when said cached entity does not exist in said datasource then;

determining when a preserve changes to said cached entity unless an original version of said cached entity is obsolete merge strategy is requested for said cached entity merging with said datasource, and

when said preserve changes to said cached entity unless said original version of said cached entity is obsolete merge strategy is requested for said cached entity merging with said datasource then;

determining when said cached entity has a current version of said cached entity having a status of added, and

when said cached entity has said current version of said cached entity having said status of added then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of other than added, and

when said cached entity has said current version of said cached entity having said status of other than added then;

removing said cached entity, and wherein a remove status related to said removing of said cached entity is stored in hardware on said computer and is displayed for a user.

14. A computer implemented method comprising:

determining when a cached entity does not exist in a datasource, and

when said cached entity does not exist in said datasource then;

determining when a preserve changes and update an original version of said cached entity merge strategy is requested for said cached entity merging with said datasource, and

when said preserve changes and update said original version of said cached entity merge strategy is requested for said cached entity merging with said datasource then;

determining when said cached entity has a current version of said cached entity having a status of unmodified, and

when said cached entity has said current version of said cached entity having said status of unmodified then;

removing said cached entity, and wherein a remove status related to said removing of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of modified, and

when said cached entity has said current version of said cached entity having said status of modified then;

 

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and changing said status of said current version of said cached entity to added, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user;

determining when said cached entity has a current version of said cached entity having a status of other than modified and having a status of other than unmodified, and;

when said cached entity has said current version of said cached entity having said status of other than modified and having said status of other than unmodified then;

 

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.

15. A computer implemented method comprising:

determining when a cached entity does not exist in a datasource, and

when said cached entity does not exist in said datasource then;

determining when a preserve said cached entity said cached entity is found in a cache merge strategy is requested for said cached entity merging with said datasource, and

when said preserve said cached entity if said cached entity is found in said cache merge strategy is requested for said cached entity merging with said datasource then;

leaving unchanged a current version of said cached entity, leaving unchanged an original version of said cached entity, and leaving unchanged said status of said current version of said cached entity, and wherein said current version of said cached entity is stored in hardware on said computer and is displayed for a user.