Patent ReferencesObject oriented data store integration environment for integration of object oriented databases and non-object oriented data facilities System and method for enabling, without recompilation, modification of class definitions and implementations in an object-oriented computer program Hierarchical encapsulation of instantiated objects in a multimedia authoring system Development system with a property-method-event programming model for developing context-free reusable software components System for generating structured query language statements and integrating legacy systems Method and apparatus for storing persistent objects on a distributed object network using a marshaling framework Object oriented programming based global registry system, method, and article of manufacture System and method for accessing data stores as objects Legacy subclassing Method and apparatus for creating a table object constructed from reusable column objects InventorApplicationNo. 09/173400 filed on 10/15/1998US Classes:707/103R, Object-oriented database structure707/102, Generating database or data structure (e.g., via user interface)707/104.1Application of database or data structure (e.g., distributed, multimedia, image)ExaminersPrimary: Alam, ShahidAssistant: Ly, Anh Attorney, Agent or FirmInternational ClassesG06F 7/00 (20060101)G06F 9/44 (20060101) Foreign Application Priority Data1998-03-16 CAAbstractIn an object oriented programming environment, an active data object accesses its stored data (such as its property and state data) by inlining the access code at the point at which access to the data on that property or state is required. Multiple access requests to the same data result in inlining the same access code in the data object multiple times. A system is thus provided to isolate the access code from active data objects in a program, to persistent wrapper objects that are reusable by one data object or many. It is the wrapper object that inlines all of the access code in a single location. Each data object user of the access code merely inlines a method invocation on the appropriate wrapper object. This reduces the size of data objects where there is now only a proliferation of single method invocations for most access request. It also simplifies the procedure for changing stored data, where only the references in individual access code blocks in wrapper objects need be changed, rather than at multiple access points throughout a data object.Other References
| |