Abstract: In an interface-based binary object system capable of supporting multiple interfaces into objects created by class templates, a relationship is defined as a pair of complementary collections on two separate interfaces, each interface found on separate objects. A link between objects is formed when an interface of one object lists an object supporting the related interface included in the object and vice versa. The collections may be of objects supporting the related interfaces or may be of specific relationship objects leading to objects supporting the related interfaces. The collections are potentially multi-valued entities that enable relationships to be established between objects according to one-to-one, many-to-one, and many-to-many architectures. By implementing a specific relationship object, behavior may be imparted to the relationship itself thereby providing more robust system behavior.

Abstract: Prefetching and caching persistent objects is disclosed. The system creates a structure context used to identify a set containing a first object and other related objects. The objects have attributes, where each attribute is identified by a name. Upon a fetch of an attribute in the first object, the system also fetches related data. The related data includes other attributes in the object, and attributes in the other objects of the set having the same name as the attribute fetched for the first object.

Abstract: In an interface-based binary object system capable of supporting multiple interfaces into objects created by class templates, a relationship is defined as a pair of complementary collections on two separate interfaces, each interface found on separate objects. A link between objects is formed when an interface of one object lists an object supporting the related interface included in the object and vice versa. The collections may be of objects supporting the related interfaces or may be of specific relationship objects leading to objects supporting the related interfaces. The collections are potentially multi-valued entities that enable relationships to be established between objects according to one-to-one, many-to-one, and many-to-many architectures. By implementing a specific relationship object, behavior may be imparted to the relationship itself thereby providing more robust system behavior.

Abstract: Prefetching and caching persistent objects is disclosed. The system creates a structure context used to identify a set containing a first object and other related objects. The objects have attributes, where each attribute is identified by a name. Upon a fetch of an attribute in the first object, the system also fetches related data. The related data includes other attributes in the object, and attributes in the other objects of the set having the same name as the attribute fetched for the first object.

Abstract: In an interface-based binary object system capable of supporting multiple interfaces into objects created by class templates, a repository of stored object states is formed that can be accessed by later created objects. Such later created objects may be of the same class as the original object or may be of a new class extended from the original class and still use the same stored object state. Access to the stored object state is made through a generic repository object that emulates the behavior of a particular class of object as defined in type definitions. Requests to a particular object's properties through interface methods are serviced by having the generic repository object make reference to the type definitions in order to fulfill the request. Binary extensibility of the generic repository object along with proper class definition in the type definitions allows custom objects having greater functionality than that provided by the generic repository object to be implemented.

Abstract: In an interface-based binary object system capable of supporting multiple interfaces into objects created by class templates, a relationship is defined as a pair of complementary collections on two separate interfaces, each interface found on separate objects. A link between objects is formed when an interface of one object lists an object supporting the related interface included in the object and vice versa. The collections may be of objects supporting the related interfaces or may be of specific relationship objects leading to objects supporting the related interfaces. By implementing a specific relationship object, behavior may be imparted to the relationship itself thereby providing more robust system behavior. Objects thus linked can be easily traversed so that convenient navigation models can be implemented allowing clients quick access to desired objects by navigating through relationships between objects.

Abstract: A computer-based method and system for generating and compressing a plurality of universally unique identifiers (UUIDs). The bits of the UUIDs are ordered from left to right. The system maintains a counter with bits ordered from a high-order bit to a low-order bit. To generate a UUID, the system increments the counter. The system then sets the right-most bits of the UUID to a node identifier, sets the next right-most bits of the UUID to a clock sequential/variant value, and sets the left-most bits of the UUID to the bits of the counter wherein the left-most bit of the UUID is set to the lowest-order bit of the counter so that sequentially generated UUIDs tend to have the same values in their right-most bits. The system then compresses these UUIDs using a suffix compression technique.

Abstract: In an interface-based binary object system capable of supporting multiple interfaces into objects created by class templates, a repository of stored object states is formed that can be accessed by later created objects. Such later created objects may be of the same class as the original object or may be of a new class extended from the original class and still use the same stored object state. Access to the stored object state is made through a generic repository object that emulates the behavior of a particular class of object as defined in type definitions. Requests to a particular object's properties through interface methods are serviced by having the generic repository object make reference to the type definitions in order to fulfill the request. Binary extensibility of the generic repository object along with proper class definition in the type definitions allows custom objects having greater functionality than that provided by the generic repository object to be implemented.