Run-time modules for dynamically adjusting computer operation

• US 6,308,326 B1
• Filed: 01/08/1999
• Issued: 10/23/2001
• Est. Priority Date: 01/08/1999
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Apple Computer Incorporated (Apple Inc.)
• Inventors: Fitzgerald-Smith, Ken, Kateley, James, Murphy, Colm J., Han, Byron
• Primary Examiner(s): Powell, Mark R.
• Assistant Examiner(s): Chavis, John Q.
• Application Number:
  US09/227,411
• Time in Patent Office: 1,019 Days
• Field of Search: 717/11
• US Class Current: 717/174
• CPC Class Codes: G06F 8/656 while running

Abstract

Code module interfaces are provided which allow a user to adjust the functionality of a program at run-time. The code module interfaces (CMIs) can be selectively activated by a user at run-time. Then, the control software will call the CMIs at various instances, for example, at startup, after each state change in the control software, at idle time and when the control software has completed all of its tasks. Alternatively, when each CMI is loaded, it can specify at which state change(s) that CMI is to be called to increase speed of operation.

Claims

1. At least one storage medium, readable by a computer, having stored thereon a computer program including at least one code module interface (CMI) defined by a first set of software code and a state machine defined by a second set of software code having a plurality of states each state having at least one predetermined exit criterion, said program executable by the computer for causing the computer to perform the steps of:

registering said at least one CMI during an initialization state of said state machine;

determining, based on said step of registering, at least one state within said state machine upon exit of which said at least one CMI is to be executed;

executing said CMI when said computer exits said at least one determined state within said computer program; and

re-entering said computer program at a state determined by said CMI, when said CMI executing step has ended, whereing functionality of said state machine is adjusted without altering said second set of software code.

2. The storage medium of claim 1, wherein said CMI determines said re-entry state independently of said state machine.

3. The storage medium of claim 1, wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said CMI is to be called.

4. The storage medium of claim 1, further comprising the steps of:

executing said CMI at another of said at least one determined states in said state machine program; and

providing a variable set of arguments associated with execution of said CMI, wherein said step of executing said CMI at said at least one determined state and said step of executing said CMI at said another of said at least one determined states are performed using different sets of arguments.

5. The storage medium of claim 1, further comprising the step of:

providing, as said CMI, a plurality of subsets of code within said first set of software code, each of which subsets are associated with a different state of said state machine.

6. The storage medium of claim 5, wherein said step of executing further comprises the step of:

running one of said subsets of said first set of software code that is associated with a state of said state machine indicated by said at least one step.

7. A storage medium, readable by a computer, having stored thereon a computer program including at least code module interface plug-in module executable by the computer for causing the computer to perform the steps of:

registering said at least one plug-in module;

determining, based on said step of registering, at least one step within said computer program wherein said at least one plug-in module is to be executed;

executing said plug-in module when said computer reaches said step within said computer program; and

allowing said plug-in module to determine a re-entry step within said computer program for re-entering said computer program when said plug-in module executing step has ended.

8. The storage medium of claim 7, wherein said plug-in module determines said re-entry step independently of said computer program.

9. The storage medium of claim 7, wherein said step of registering further comprises the step of:

providing, by said CMI, a mask which identifies state transitions at which said plug-in module is to be called.

10. The storage medium of claim 7, further comprising the steps of:

executing said plug-in module at another step in said computer program; and

providing a variable set of arguments associated with execution of said plug-in module, wherein said step of executing said plug-in module at said at least one step and said step of executing said plug-in module at said another step are performed using different sets of arguments.

11. The storage medium of claim 7, further comprising the step of:

providing, as said plug-in module, a plurality of sets of code, each of which are associated with a different state of said computer program.

12. The storage medium of claim 11, wherein said step of executing further comprises the step of:

running one of said sets of code that is associated with a state of said computer program indicated by said at least one step.

13. A method for adjusting the functionality of software code without altering the software code itself, said software code defining a plurality of states, each state having at least one predetermined exit criterion, said method comprising the steps of:

storing at least one code interface module (CMI) on a computer readable medium in a predetermined memory location;

launching said software code;

registering, by said software code, said CMI including identifying a state within said software code upon exit of which said CMI is to be run;

running said CMI after said at least one predetermined exit criterion associated with said identified state has been satisfied; and

returning to a state within said software code determined by said CMI after said CMI has finished running.

14. The method of claim 13, wherein said functionality of said software code includes downloading software to a computer and said CMI operates to perform an audit on said downloaded software.

15. The method of claim 13, wherein said step of storing further comprises the step of:

providing a user interface for identifying selectable CMIs for run-time operation with said software code; and

selecting, by a user said CMI from said identified selectable CMIs.

16. The method of claim 13, wherein said step of registering further comprises:

providing, by said CMI, a mask which identifies state transitions at which said CMI is to be called.