Deterministic memory management in a computing environment

Abstract

Systems and methods for memory management in a computing environment are provided. The method comprises monitoring instantiation of objects during a web session established between a client applet and a server over the world wide web, wherein the client applet submits requests to the server and one or more objects are instantiated by a servlet application running on the server to service the submitted requests, wherein server memory space is allocated to said one or more objects instantiated by the servlet; determining execution scope of a first object instantiated by a servlet, in response to the server receiving a request from the client applet, wherein the execution scope of the first object is determined according to a context in which the first object is instantiated.

1 - 20 . (canceled) 
     
     
         21 . A memory management method implemented for execution by one or more processors, the method comprising:
 monitoring instantiation of objects during a web session established between a client applet and a server over the world wide web, wherein the client applet submits requests to the server and one or more objects are instantiated by a servlet application running on the server to service the submitted requests, wherein server memory space is allocated to said one or more objects instantiated by the servlet;   determining execution scope of a first object instantiated by the servlet, in response to the server receiving a request from the client applet, wherein the execution scope of the first object is determined according to a context in which the first object is instantiated, wherein the context is defined based on a runtime flow of the servlet as managed by the servlet's web container implemented to define the runtime environment and detect application, task, and task specific components of the servlet; and   deallocating the server memory space allocated to the first object, in response to determining that the execution scope of the first object has expired.   
     
     
         22 . The method of  claim 21 , wherein execution scope of the first object is defined according to the following three contexts: (1) application context, (2) task/subtask context and (3) current context. 
     
     
         23 . The method of  claim 22 , wherein if the first object is associated with the servlet application, the first object is not deallocated from the server memory space until at least one of the servlet application or the session is terminated. 
     
     
         24 . The method of  claim 23 , wherein if the first object is associated with a task of the servlet application, the first object is not deallocated from the server memory space until at least one of the task or the servlet application or the session is terminated. 
     
     
         25 . The method of  claim 24 , wherein if the first object is associated with a subtask of the task, the first object is not deallocated from the server memory space until at least one of the subtask or the task or the servlet application or the session is terminated. 
     
     
         26 . The method of  claim 25 , wherein if the first object is associated with a component of a task or a subtask, the first object is not deallocated from the server memory space while said component remains active. 
     
     
         27 . The method of  claim 26 , wherein the runtime flow of the servlet application is monitored by a framework software implemented in the servlet's web container. 
     
     
         28 . The method of  claim 27 , wherein the framework comprises a set of related classes used for detecting the runtime flow of the servlet application and for monitoring active tasks and corresponding components. 
     
     
         29 . The method of  claim 28 , wherein the set of classes in the framework are utilized to determine tasks that are active in the current context or tasks that are currently displayed to a user. 
     
     
         30 . The method of  claim 28 , wherein the set of classes in the framework are utilized to determine currently active components for each task, and the flow in which said components were viewed by a user. 
     
     
         31 . A memory management system comprising:
 one or more processors for controlling memory management operations;   a logic unit for monitoring instantiation of objects during a web session established between a client applet and a server over the world wide web, wherein the client applet submits requests to the server and one or more objects are instantiated by a servlet application running on the server to service the submitted requests, wherein server memory space is allocated to said one or more objects instantiated by the servlet;   a logic unit for determining execution scope of a first object instantiated by the servlet, in response to the server receiving a request from the client applet, wherein the execution scope of the first object is determined according to a context in which the first object is instantiated, wherein the context is defined based on a runtime flow of the servlet as managed by the servlet's web container implemented to define the runtime environment and detect application, task, and task specific components of the servlet; and   a logic unit for deallocating the server memory space allocated to the first object, in response to determining that the execution scope of the first object has expired.   
     
     
         32 . The system of  claim 31 , wherein execution scope of the first object is defined according to the following three contexts: (1) application context, (2) task/subtask context and (3) current context. 
     
     
         33 . The system of  claim 32 , wherein if the first object is associated with the servlet application, the first object is not deallocated from the server memory space until at least one of the servlet application or the session is terminated. 
     
     
         34 . The system of  claim 23 , wherein if the first object is associated with a task of the servlet application, the first object is not deallocated from the server memory space until at least one of the task or the servlet application or the session is terminated. 
     
     
         35 . The system of  claim 24 , wherein if the first object is associated with a subtask of the task, the first object is not deallocated from the server memory space until at least one of the subtask or the task or the servlet application or the session is terminated. 
     
     
         36 . The system of  claim 25 , wherein if the first object is associated with a component of a task or a subtask, the first object is not deallocated from the server memory space while said component remains active. 
     
     
         37 . The system of  claim 26 , wherein the runtime flow of the servlet application is monitored by a framework software implemented in the servlet's web container. 
     
     
         38 . The system of  claim 27 , wherein the framework comprises a set of related classes used for detecting the runtime flow of the servlet application and for monitoring active tasks and corresponding components. 
     
     
         39 . A computer program product comprising a non-transitory data storage medium having a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:
 monitor instantiation of objects during a web session established between a client applet and a server over the world wide web, wherein the client applet submits requests to the server and one or more objects are instantiated by a servlet application running on the server to service the submitted requests, wherein server memory space is allocated to said one or more objects instantiated by the servlet;   determine execution scope of a first object instantiated by the servlet, in response to the server receiving a request from the client applet, wherein the execution scope of the first object is determined according to a context in which the first object is instantiated, wherein the context is defined based on a runtime flow of the servlet as managed by the servlet's web container implemented to define the runtime environment and detect application, task, and task specific components of the servlet; and   deallocate the server memory space allocated to the first object, in response to determining that the execution scope of the first object has expired.   
     
     
         40 . The computer program product of  claim 39 , wherein execution scope of the first object is defined according to the following three contexts: (1) application context, (2) task/subtask context and (3) current context.