Loading patent…
AssigneeSap SE
InventorsFrank Brunswig, Ioannis Grammatikakis, Dinu Pavithran, Guenter Pecht-Seibert, Michael Picht, Alexander Rauh, Holger Schmidt
Estimating the term…
A system and method for message lifetime management. According to an embodiment of the invention, a front-end application process identifies during a user interface interaction cycle of the front-end application process at least one stateful message reported to the front-end application process by a back-end service process during a prior user interface interaction cycle of the front-end application process, the at least one stateful message having been stored in a message buffer by the front-end application process, queries the back-end service process to determine whether the at least one stateful message is currently valid, and removes the at least one stateful message from the message buffer if it is determined not to be currently valid.
A method for message lifetime management, comprising:
A system for message lifetime management, comprising:
A non-transitory computer readable storage medium storing thereon program instructions that, when executed, cause an executing device to:
Dependencies are inferred from the claim text.
Drawings are temporarily unavailable. Open the PDF at USPTO
From the US filing history. Foreign family members aren’t listed.
No references of this kind are recorded.
Interprogram communication: event management; Broadcasting; Multicasting; Notifications
Indexing scheme relating to G06F9/54: local
Indexing scheme relating to G06F9/54: gui
Computing and data processing
About 3 years 2 months of term left · ends 15 Dec 2029 (estimated)
Development of a complex software system usually involves defining an object model that represents the desired structure and functionality of objects to be implemented in an application framework. In business software environments, these objects are sometimes referred to as business objects, which can be defined according to a node structure that may specify corresponding data elements and behaviors to be associated with the objects.
Once the object model is defined, developers are able to produce code for the application framework that implements the defined objects. The application framework acts as a service provider and generally provides the back-end level functionality for the software system. Once completed, developers are then able to code the front-end aspects of the software system, such as the user interface portion of the system providing specific application contexts and usage scenarios, which hooks into and depends upon the back-end level functionality.
Because the back-end functionality of such systems is designed to support diverse front-end components, the back-end is often not aware of the front-end's specific application context and usage scenario when responding to a service call from the front-end. This lack of awareness can lead to unfavorable message handling issues for the front-end component in connection with stateful messages, which are relevant beyond the period of the particular call.
FIG. 1 is a block diagram that depicts a system architecture in accordance with an embodiment of the present invention.
FIG. 2 is a process flow diagram that depicts a message lifetime management process in accordance with an embodiment of the present invention.
FIG. 3 is a process flow diagram that depicts a message lifetime management process in accordance with an embodiment of the present invention.
Embodiments of the present invention reduce the unfavorable message handling issues between front-end and back-end system components by providing a front-end component that stores and manages the lifetime of stateful back-end messages. The front-end component continually confirms the validity of the stateful back-end messages prior to displaying them to the user, thus minimizing the display of inappropriate or invalid messages to the end user.
FIG. 1 depicts a front-end and back-end system architecture in accordance with an embodiment of the present invention. A front-end runtime environment (100) includes an application process (120) in communication with a user interface process (130) and a message buffer (140). A back-end runtime environment (110) includes a service process (150) in communication with the application process (120).
FIG. 2 depicts a message lifetime management process in accordance with an embodiment of the present invention, which occurs during a user interface interaction cycle (220)—the period between the application process (120) receiving (200) the process flow from the user interface process (130) and returning (210) the process flow to the user interface process (130).