US2016283252A1PendingUtilityA1

Dynamic execution environment in network communications

57
Assignee: SYNACTIVE INCPriority: Jul 27, 2012Filed: Mar 25, 2016Published: Sep 29, 2016
Est. expiryJul 27, 2032(~6.1 yrs left)· nominal 20-yr term from priority
Inventors:Thomas Ewe
G06F 9/451G06F 3/0486H04L 43/045G06F 9/4443H04L 67/561
57
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A computer-implemented system and method for providing a dynamic execution environment. In an embodiment, the system and method comprises receiving a base user interface from a server, creating and storing one or more intermediate representations (IRs) which represent a mapping between the base user interface and a modified user interface, executing the one or more IRs to intercept network communication from the server, map between the base user interface and the modified user interface, and send the modified user interface to one or more clients, and executing the one or more IRs to intercept network communication from the one or more clients to the server with user data, map between the modified user interface and the base user interface, and send the base user interface and the user data to the server.

Claims

exact text as granted — not AI-modified
1 . (canceled) 
     
     
         2 . A computer-implemented method for providing an event-trapping mechanism in a dynamic execution environment, the method comprising, by at least one hardware processor:
 creating one or more execution blocks from a function stored in a script, wherein each of the one or more execution blocks is associated with a sequence of screen events of a user interface;   storing the one or more execution blocks as handlers; and   executing at least one of the one or more handlers independently from the others, when the associated sequence of screen events for the handler is detected in network traffic.   
     
     
         3 . The method of  claim 2 , wherein the sequence of screen events is one or more of an on-screen event, an on-error event, and an on-message event. 
     
     
         4 . The method of  claim 2 , wherein an entry event for the function is stored in an event array which associates events with functions. 
     
     
         5 . The method of  claim 2 , wherein the one or more handlers exist in one or more sequences of screen events. 
     
     
         6 . The method of  claim 2 , wherein the script contains goto statements for moving between the one or more handlers. 
     
     
         7 . The method of  claim 2 , wherein the associated sequence of screen events are document object model events. 
     
     
         8 . The method of  claim 2 , wherein the network traffic is traffic between a client and a server such that the dynamic execution environment is an intermediary monitoring the network traffic. 
     
     
         9 . The method of  claim 8 , wherein the handlers are stored in a memory of the dynamic execution environment. 
     
     
         10 . A system for providing an event-trapping mechanism in a dynamic execution environment, comprising:
 at least one hardware processor configured to perform the steps comprising:
 creating one or more execution blocks from a function stored in a script, 
   wherein each of the one or more execution blocks is associated with a sequence of screen events of a user interface;
 storing the one or more execution blocks as handlers; and 
 executing at least one of the one or more handlers independently from the others, when the associated sequence of screen events for the handler is detected in network traffic. 
   
     
     
         11 . The system of  claim 10 , wherein the sequence of screen events is one or more of an on-screen event, an on-error event, and an on-message event. 
     
     
         12 . The system of  claim 10 , wherein an entry event for the function is stored in an event array which associates events with functions. 
     
     
         13 . The system of  claim 10 , wherein the one or more handlers exist in one or more sequences of screen events. 
     
     
         14 . The system of  claim 10 , wherein the script contains goto statements for moving between the one or more handlers. 
     
     
         15 . The system of  claim 10 , wherein the associated sequence of screen events are document object model events. 
     
     
         16 . The system of  claim 10 , wherein the network traffic is traffic between a client and a server such that the dynamic execution environment is an intermediary monitoring the network traffic. 
     
     
         17 . The method of  claim 16 , wherein the handlers are stored in a memory of the dynamic execution environment.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.