Mechanism for dynamic selection of an object's method

• US 6,487,714 B1
• Filed: 05/24/1999
• Issued: 11/26/2002
• Est. Priority Date: 05/24/1999
• Status: Expired due to Term

• Current Assignee: LinkedIn Corporation (Microsoft Corporation)
• Original Assignee: International Business Machines Corporation
• Inventors: Azagury, Alain Charles, Factor, Michael, Porat, Sara, Teperman, Avi
• Primary Examiner(s): Dam, Tuan Q.
• Assistant Examiner(s): KENDALL, CHUCK O
• Application Number:
  US09/317,421
• Time in Patent Office: 1,282 Days
• Field of Search: 717/108, 717/140, 717/151, 717/153, 717/158, 717/116, 717/165, 709/217, 709/332
• US Class Current: 717/116
• CPC Class Codes: G06F 9/449 Object-oriented method invocation or resolution

Abstract

A data structure and associated mechanism for implementing object oriented programming language, comprising at least two code blocks for at least one method of an object of a specified class, each of the code blocks containing a different implementation of the at least one method. An access mechanism is provided for accessing a desired code block at run-time on a per object instance basis so as to allow selection of a desired implementation of the at least one method without requiring instantiation of an object of a different class. The selection of which implementation to invoke is integrated into an existing invocation method of the language and is thus transparent to a calling application invoking the method.

Claims

1. A computer program product comprising:

a computer usable medium having computer readable program code embodied therein for implementing an object oriented programming language, the computer readable program code comprising;

(a) computer readable program code in respect of at least two code blocks for at least one method of an object of a specified class, each of said code blocks containing a different implementation of said at least one method, and

(b) computer readable program code for accessing a desired code block at run-time on a per object instance basis so as to allow selection of a desired implementation of said at least one method without requiring instantiation of an object of a different class;

said selection of which implementation to invoke being integrated into an existing invocation method of said language and thus being transparent to a calling application invoking said at least one method.

2. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism responsive to data external to the object for selecting the desired implementation.

3. The product of claim 2, wherein said data external to the object is a function of a system attribute or state.

4. The product of claim 3, wherein the system attribute or state relates to a system resource, thus enabling different code blocks to be executed depending on system resource constraints.

5. The product of claim 2, wherein the data external to the object is indicative of a pragmatic behavior, so as to allow different pragmatic behaviors to be associated with said method for each object that is an instance of the specified class.

6. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism that includes a parameter per object in respect of each method of the specified class so as to allow independent selection of each method in the class for each object that is an instance of the class.

7. The product of claim 6, wherein the access mechanism is responsive to a calling program for selectively implementing a test coverage strategy in respect of one or more methods of the object.

8. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism that allows different implementations for a method of an object to be executed at different points in the lifetime of the object.

9. The product of claim 1, wherein a first one of said code blocks relates to an implementation of the method for a master object and a second one of said code blocks relates to an implementation of the method for a proxy object, thus allowing a distributed program running on a cluster of machines to change the implementation of an object from master to proxy or vice versa during run-time in a manner which is transparent to an application invoking said method.

10. The product of claim 9, being used by a caching program for implementing different cache strategies according to an instance of the object.

11. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism that is responsive to an optimization program for implementing different optimization strategies according to an instance of the object.

12. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism that employs pointers to point to a desired one of the code blocks.

13. The product of claim 1, wherein the program code for accessing a desired code block includes an access mechanism that uses an index for accessing a desired one of the code blocks.

26. The computer program product according to claim 1, wherein said at least two code blocks containing different implementations of said at least one method co-exist at run-time.

14. A program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform method steps for implementing an object oriented programming language, said method steps comprising:

(a) providing at least two code blocks for at least one method of an object of a specified class, each of said code blocks containing a different implementation of said at least one method, and

(b) accessing a desired code block at run-time on a per object instance basis so as to allow selection of a desired implementation of said at least one method without requiring instantiation of an object of a different class;

said selection of which implementation to invoke being integrated into an existing invocation method of said language and thus being transparent to a calling application invoking said at least one method.

15. The device of claim 14, wherein step (b) includes accessing data external to the object for selecting the desired implementation.

16. The device of claim 15, wherein step (b) includes deriving said data external to the object as a function of a system attribute, state or resource constraint thus enabling different method code to be executed depending on said system attribute, state or resource constraints.

17. The device of claim 14, wherein step (a) includes defining a parameter per object in respect of each method of the specified class so as to allow independent selection of each method in the class for each object that is an instance of the class.

18. The device of claim 17, wherein step (b) includes accessing a calling program for selectively implementing a test coverage strategy in respect of one or more methods of the object.

19. The device of claim 14, wherein step (b) includes accessing different implementations for a method of an object to be executed at different points in the lifetime of the object.

20. The device of claim 14, wherein:

a first one of said code blocks relates to an implementation of the method for a master object and second one of said code blocks relates to an implementation of the method for a proxy object, and

step (b) is performed by a run-time system supporting a distributed program running on a cluster of machines to change the implementation of an object from master to proxy or vice versa during run-time in a manner which is transparent to an application invoking said method.

21. The device of claim 14, being used by a caching program for implementing different cache strategies according to an instance of the object.

22. The device of claim 14, wherein step (b) includes defining a parameter indicative of a pragmatic behavior, so as to allow different pragmatic behaviors to be associated with said method for each object that is an instance of the specified class.

23. The device of claim 14, wherein step (b) includes accessing an optimization program for implementing different optimization strategies according to an instance of the object.

24. The device of claim 14, wherein step (b) includes using pointers to point to a desired one of the code blocks.

25. The device of claim 14, wherein step (b) includes using an index for accessing a desired one of the code blocks.

27. The program storage device according to claim 14, wherein said at least two code blocks containing different implementations of said at least one method co-exist at run-time.