Importance

Loading Importance Indicators...

Abstract

A solution may be provided in which a cache may assign a version to each object that it caches. The version may be saved in a database along with the object. Each time the business logic accesses the cache for a dependent object, such as a read from the bit mask field of the new parent member, the version of the object checked in the cache and its identification may be saved on a dependency list. Once changes to the object are performed, the business logic may issue a commit command. The cache may then verify that the version of each object on the dependency list matches the version that is in the database. If an object on the dependency list either does not exist in the database, or exists with another version, then the transaction may be canceled.

Loading the Abstract Image...

First Claim