Transaction Execution System Interface and Enterprise System Architecture Thereof

Abstract

A system for interfacing at least one user interactive device with a trade execution system to execute trading transactions requested by users over a network includes an application in communication with the network for interfacing between the at least one user interactive device and the trade execution system and coordinating interaction of the at least one user interactive device with the trade execution system. The application contains first and second APIs. The first API is structured to deliver a trading transaction request received from the at least one user interactive device to the trade execution system. The second API is structured to deliver real-time information relating to the trading transaction request received from the trade execution system to the at least one user interactive device. The first API includes at least one stub that is called by the application at a predefined step during processing of the trading transaction request. The at least one stub includes code to interface the application with the trade execution system.

1 . A method of interfacing between a client and an application server across a network, comprising the step of providing a browser to interface the client with the application server, wherein the browser is based on a screen definition language that allows every screen to be independent of other screens and every element of the screen to be independent from other elements. 
     
     
         2 . A method as in  claim 1 , wherein the application server is structured and configured to convert the screen definition language to another set of screen definition language on-the-fly so that the application server may communicate with clients that use browsers that are compatible with said another set of screen definition language. 
     
     
         3 . A method as in  claim 2 , wherein said another set of screen definition language is a markup language. 
     
     
         4 . A method as in  claim 3 , wherein said markup language includes HTML or HDML. 
     
     
         5 . A method as in  claim 1 , wherein screen layout information is stored at the client, wherein the browser renders the screen based on the data sent from the server and the stored screen layout information. 
     
     
         6 . A method as in  claim 5 , wherein the application server includes one or more screen layout templates each based on a screen layout information, and wherein the screen layout templates are used to create screen data to be sent to the client. 
     
     
         7 . A method as in  claim 6 , wherein the screen data sent from the server excludes screen layout information. 
     
     
         8 . A method as in  claim 1  further comprising the steps of:
 when an element in the browser is edited by the client, setting the value of the variable assigned to the edited element; and   sending only the value of the variable to the server to represent the edited element.   
     
     
         9 . A method as in  claim 1  wherein the browser is device dependent and the variable sent from the server is device independent, which variable can be recognized by the device dependent browser. 
     
     
         10 . A method of distributing screen information between a client and an application server across a network, comprising the steps of:
 providing a device dependent browser to interface the client with the application server, wherein the device dependent browser is associated with a screen layout;   transmitting screen information from the server to the client in a device independent fashion, wherein the screen information is based on a screen layout template stored at the server;   presenting the screen information at the client using the device dependent browser and based on the screen layout.