Methods for transparent management of context and state in an asynchronous callback flow

• US 9,262,156 B2
• Filed: 02/12/2014
• Issued: 02/16/2016
• Est. Priority Date: 02/12/2014
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Dvinsky, Alexander, Roytman, Alexey, Shachor, Gal, Shagin, Konstantin, Wasserman, Bruno
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): ST LEGER, GEOFFREY R
• Application Number:
  US14/178,288
• Publication Number:
  US 20150227362A1
• Time in Patent Office: 734 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: G06F 8/30 Creation or generation of source code
• CPC Class Codes: G06F 8/31 Programming languages or programming paradigms
• CPC Class Codes: G06F 8/40 Transformation of program code
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 9/461 Saving or restoring of program or task context
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: G06F 9/541 via adapters, e.g. between incompatible applications

Abstract

Computerized methods for providing one or more memory values present in memory during execution of a procedure to be automatically available to an asynchronous callback executed later. The methods comprise receiving a code containing procedures, the procedures having input parameters to be executed as asynchronous callback procedures. The methods further comprise replacing the procedures in the code with wrapper procedures, where the wrapper procedures comprise instructions for storing one or more memory values, storing the asynchronous callbacks of the input parameters, replacing each of the input parameters with a wrapper callback, the wrapper callback comprising instruction for restoring the memory values and executing the asynchronous callbacks. The methods further comprise executing the original procedures. The methods further comprise executing the code with the wrapper procedures, providing the memory values present during execution of the procedure to be automatically available to the asynchronous callback executed later.

Claims

1. A computerized method for providing at least one memory value present in computer memory during execution of a program procedure to be automatically available to an asynchronous callback procedure executed later, comprising:

receiving a code containing at least one program procedure, said at least one program procedure having at least one input parameter to be executed as an asynchronous callback procedure;

replacing said at least one program procedure in said code with at least one wrapper procedure, where each of said at least one wrapper procedure comprises instructions for;

storing at least one memory value available to said asynchronous callback procedure prior to execution of said asynchronous callback procedure;

storing said asynchronous callback procedure of said at least one input parameter;

replacing each of said at least one input parameter with a wrapper callback procedure, said wrapper callback procedure comprising instructions for restoring said at least one memory value and then executing said asynchronous callback procedure; and

executing said at least one program procedure;

executing said code with said at least one wrapper procedure, providing said at least one memory value present during execution of said program procedure to be automatically available to said asynchronous callback procedure executed later,

wherein execution of said asynchronous callback procedure initiates execution of at least one additional callback procedure, and each of said at least one additional callback procedure is performed by execution of corresponding said wrapper callback procedure which restores said at least one memory value prior to execution of said at least one additional callback procedure.

2. The method of claim 1, wherein said at least one wrapper procedure and said wrapper callback procedure are made available by at least one computerized interface of the types from a list of a source code file, a binary machine instruction file, a header file, a driver file, a library file, a compiled library file, and a remote procedure call.

3. The method of claim 1, wherein said at least one memory value comprises any data value from the list of local variable values, global variable values, local variable address values, global variable address values, state machine status data values, time data values, date data values, user identification data values, user input data values, server-side computer data values, client-side computer data values, server-side program computer data values, client-side program data values, billing information data values, processor thread information data values, counter data values, procedure timing data values, exception handling data values, system monitoring data values, and resource management data values.

4. The method of claim 1, wherein said at least one program procedure, said at least one asynchronous callback procedure, said at least one wrapper procedure, and said wrapper callback procedure are developed in a programming environment coded according to the programming syntax of at least one from a list of programming languages including Javascript, C#, .NET, Ruby, D, Python, Perl, Java, Groovy, and Scala.

5. The method of claim 4, wherein said programming environment is at least one from a list of Node.js, Tornado, Twisted, Perl Object Environment, libevent, Vert.x, Akka, EventMachine, and vibe.d.

6. The method of claim 1, wherein said at least one wrapper procedure additionally stores a mapping between said at least one asynchronous callback procedure and said wrapper callback procedure for use in a manipulation of at least one callback flow, and a manipulating wrapper procedure uses said mapping to manipulate said at least one callback flow.

7. The method of claim 6, wherein said manipulation comprises any from the list of priority assignment, and cancelling.

8. The method of claim 1, wherein the term procedure may refer to any from the list of a subroutine, a function, and a routine, as used in procedural programming languages.

9. A computer program product, comprising a non-transitory computer usable memory having a computer readable program code embodied therein, said computer readable program code containing processor instructions to implement a method for providing at least one memory value present in computer memory during execution of a program procedure to be automatically available to an asynchronous callback procedure executed later, comprising instructions for:

receiving a code containing at least one program procedure, said at least one program procedure having at least one input parameter to be executed as an asynchronous callback procedure;

replacing said at least one program procedure in said code with at least one wrapper procedure, where each of said at least one wrapper procedure comprises instructions for;

storing at least one memory value available to said asynchronous callback procedure prior to execution of said asynchronous callback procedure;

storing said asynchronous callback procedure of said at least one input parameter;

replacing each of said at least one input parameter with a wrapper callback procedure, said wrapper callback procedure comprising instructions for restoring said at least one memory value and then executing said asynchronous callback procedure; and

executing said at least one program procedure;

executing said code with said at least one wrapper procedure, providing said at least one memory value present during execution of said program procedure to be automatically available to said asynchronous callback procedure executed later,

wherein execution of said asynchronous callback procedure initiates execution of at least one additional callback procedure, and each of said at least one additional callback procedure is executed by corresponding said wrapper callback procedure which restores said at least one memory value prior to execution of said at least one additional callback procedure.

10. The computer program product of claim 9, wherein said at least one wrapper procedure and said wrapper callback procedure are made available by at least one computerized interface of the types from a list of a source code file, a binary machine instruction file, a header file, a driver file, a library file, a compiled library file, and a remote procedure call.

11. The computer program product of claim 9, wherein said at least one memory value comprises any data value from the list of local variable values, global variable values, local variable address values, global variable address values, state machine status data values, time data values, date data values, user identification data values, user input data values, server-side computer data values, client-side computer data values, server-side program computer data values, client-side program data values, billing information data values, processor thread information data values, counter data values, procedure timing data values, exception handling data values, system monitoring data values, and resource management data values.

12. The computer program product of claim 9, wherein said at least one program procedure, said at least one asynchronous callback procedure, said at least one wrapper procedure, and said wrapper callback procedure are developed in a programming environment coded according to the programming syntax of at least one from a list of programming languages including Javascript, C#, .NET, Ruby, D, Python, Perl, Java, Groovy, and Scala.

13. The computer program product of claim 9, wherein said programming environment is at least one from a list of Node.js, Tornado, Twisted, Perl Object Environment, libevent, Vert.x, Akka, EventMachine, and vibe.d.

14. The computer program product of claim 9, wherein said at least one wrapper procedure additionally stores a mapping between said at least one asynchronous callback procedure and said wrapper callback procedure for use in cancelling at least one callback flow, and a cancelling wrapper procedure uses said mapping to cancel said at least one callback flow.

15. The computer program product of claim 9, wherein the term procedure may refer to any from the list of a subroutine, a function, and a routine, as used in procedural programming languages.

16. A computerized device for providing at least one memory value present in computer memory of the computerized device during execution of a program procedure to be automatically available to an asynchronous callback procedure executed later, comprising:

at least one hardware processor configured for executing the following code instructions;

first code instructions for receiving a code containing at least one program procedure, said at least one program procedure having at least one input parameter to be executed as an asynchronous callback procedure;

second code instructions for replacing said at least one program procedure in said code with at least one wrapper procedure, where each of said at least one wrapper procedure comprises code instructions for;

storing at least one memory value available to said asynchronous callback procedure prior to execution of said asynchronous callback procedure;

storing said asynchronous callback procedure of said at least one input parameter;

replacing each of said at least one input parameter with a wrapper callback procedure, said wrapper callback procedure comprising instructions for restoring said at least one memory value and then executing said asynchronous callback procedure; and

executing said at least one program procedure;

third code instructions for executing said code with said at least one wrapper procedure, providing said at least one memory value present during execution of said program procedure to be automatically available to said asynchronous callback procedure executed later,

wherein execution of said asynchronous callback procedure initiates execution of at least one additional callback procedure, and each of said at least one additional callback procedure is executed by corresponding said wrapper callback procedure which restores said at least one memory value prior to execution of said at least one additional callback procedure.

17. The computerized device of claim 16, further comprising a computer housing for containing said at least one hardware processor, said at least one input and output interface, and said at least one user interface, said computer housing configured to operate in the environment the device is located in.

18. The computerized device of claim 16, wherein the term procedure may refer to any from the list of a subroutine, a function, and a routine, as used in procedural programming languages.