US 7,624,131 B2 · Type restriction and mapping for partial materialization

Abstract

Described is a collection of type versions (objects) associated with an application program that lists only those type versions that can be bound to an application program. This ensures stability and security by preventing other type versions from being bound to the application program, unless overridden by policy. A type binding process only materializes objects for stored types that correspond to matching type versions in the application's known types collection. The type may be loaded from a local folder, or from a global cache, providing installation flexibility. A data container accessible to the application may be populated with data for fields defined on a type in the collection having a version not bound to the application program, and for fields of a related type not maintained in the collection. Default values are used to populate any unpopulated fields when policy specifies that a different type version be used.

Claims20

Dependent claims

A computer-readable storage medium having computer-executable instructions that, when executed, cause a computer to perform a computer-implemented method comprising:

binding an application program to a collection populated with a set of known types including version information against which the application program has been tested;
determining whether to restrict materialization of a particular type instance persisted in a serialized state within a data store by evaluating the set of known types including version information that is maintained in the collection associated with the application program against metadata of the particular type instance that is accessible to the application program;
materializing the type instance as an object bound to the application program only when the identified type including the version information maintained in the collection matches the metadata;
restricting the materialization of the particular type instance when the identified type including the version information maintained in the collection does not match the metadata;
and
maintaining non-materialized data for a restricted type instance in a data container comprising a bit bucket that is read-only to the application program.

3 more elements

In a computing environment, a system comprising:

at least one data store on a computer, each data store containing a set of type instances persisted in a serialized state;
and
a type binding process coupled to each data store and to an application program on the computer that is bound to a collection populated with a set of known type versions against which the application program has been tested, the binding process configured to materialize objects corresponding to persisted type instances in the data store for binding to the application program, in which the binding process:
determines whether to restrict materialization of a particular object within the data store by evaluating the set of known type versions maintained in the collection associated with the application program against metadata corresponding to the type version of the particular object,
only materializes objects that correspond to matching type versions provided in the collection of known type versions, except when overridden by policy,
restricts materialization of objects when the type versions of the objects do not match the known type versions maintained in the collection, and
maintains non-materialized data for restricted objects in a data container comprising a bit bucket that is read-only to the application program.

4 more elements

Dependencies are inferred from the claim text.

Type restriction and mapping for partial materialization

Life of this patent

Type restriction and mapping for partial materialization

Life of this patent

Abstract

Claims20