Binary compatible software objects

• US 6,971,087 B2
• Filed: 10/04/2002
• Issued: 11/29/2005
• Est. Priority Date: 06/03/1998
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Knapton, Kenneth S. III
• Primary Examiner(s): CHAVIS, JOHN Q
• Application Number:
  US10/264,733
• Publication Number:
  US 20030033447A1
• Time in Patent Office: 1,152 Days
• Field of Search: 717/116
• US Class Current: 717/116
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548

Abstract

An object oriented programming technology enables multiple objects to be snapped into a given container or client. Thus, for example, multiple ActiveX controls can be snapped into one given container and these controls may be accessed in a fashion which can be truly termed binary compatible. That is, each of the controls can be accessed without requiring recompiling even when they have different identifiers and/or different interfaces. In one embodiment, this may be accomplished by providing SetGUID and GetGUID functions in a layer class associated with the objects. The identifier of the desired object can be obtained from the system database and set in the layer class to selectively access one of at least two objects in the same container without recompiling.

Claims

1. A method for object oriented programming comprising:

creating a first object having a first identifier, said object associated with a first client;

providing a second object having a second identifier, said second object associated with the first client, said first and second identifiers being different; and

using said second object with said first client in place of the first object without recompiling.

2. The method of claim 1 including creating a first COM object having a first globally unique identifier, said first COM object associated with a first container, inserting a second COM object having a second globally unique identifier, said second COM object associated with the first container, the first and second globally unique identifiers being different, and using said second COM object with the first container without recompiling.

3. The method of claim 2 including providing a layer class and setting said globally unique identifier in said layer class.

4. The method of claim 1 including creating a layer class that interfaces with one of a plurality of globally unique identifiers of objects associated with said layer class.

5. The method of claim 1 including using said first object again with said first client in place of said second object without recompiling.

6. A method for object oriented programming comprising:

registering a first object with a first globally unique identifier;

registering a second object with a second globally unique identifier; and

selectively accessing one of said first and second objects without recompiling.

7. The method of claim 6 including creating a source code version of said objects, and programming said globally unique identifiers into a layer class.

8. The method of claim 7 including getting the globally unique identifier for each object from a database and setting each globally unique identifier in said layer class.

9. A container for a software object comprising:

one or more objects, said container adapted to selectively work with first and second objects having different identifiers.

10. The container of claim 9 including a layer class adapted to selectively utilize the identifier of either said first or second object.

11. The container of claim 10 wherein said layer class includes a first function that obtains globally unique identifiers from a system database and a second function that sets globally unique identifiers in the layer class.

12. A computer readable storage medium for storing a program including instructions for causing a computer to:

create an object having a first identifier, said object associated with a first client;

provide a second object having a second identifier, said second object associated with the first client, said first and second identifiers being different; and

use said second object with said first client in place of said first object without recompiling.

13. The medium of claim 12 wherein said objects are COM objects.

14. The medium of claim 13 wherein said COM objects are ActiveX controls.

15. The medium of claim 13 wherein said identifiers are globally unique identifiers.

16. The medium of claim 15 including one or more instructions for storing a program instructions for causing a computer to create a layer class having selectively programmable globally unique identifiers for more than one object.

17. The medium of claim 16 including instructions for causing a computer to obtain globally unique identifiers and setting the identifiers in the layer class.