Web applications having end-user data isolated in the local domain

Abstract

A session for a Web application can be established between a Web server of a Web domain and a browser of a client of a local domain. The Web application can be constructed so that view and controller functionality are provided by components executing in the Web domain and where model functionality is provided by components executing in the local domain. During the session, an expeditor runtime component can be served from the Web domain to the local domain for the Web application session. At least one widget can be served from the Web domain to the local domain, where the widgets execute within an instance of the expeditor runtime. End-user data utilized by the Web application can be isolated within the local domain so that it is not exposed to the Web domain.

1 - 20 . (canceled) 
     
     
         21 . A computer-implemented method for implementing a Web application within a client of a local domain, comprising:
 establishing, between a Web server of a Web domain and a browser of the client, an application session for the Web application;   serving, from the Web domain to the local domain, a widget and an expeditor runtime component configured to execute the widget; and   executing components of the Web application within the Web domain, wherein the widget processes end-user data that is
 utilized by the Web application within the local domain and 
 isolated from the Web domain. 
   
     
     
         22 . The method of  claim 21 , wherein
 the Web application includes model, view, and controller functionality,   the view and controller functionality are provided by the components of the Web application executing in the Web domain, and   the model functionality is provided by components of the Web application executing in the local domain.   
     
     
         23 . The method of  claim 22 , wherein
 the expeditor runtime component provides the model functionality.   
     
     
         24 . The method of  claim 21 , wherein
 the expeditor runtime component executes in a different physical device from the client, and   a bridge exposes functionality of the expeditor runtime component to the Web application rendered in the browser.   
     
     
         25 . The method of  claim 21 , wherein
 the end-user data is stored within a data store located within the local domain and in a different physical device from the client.   
     
     
         26 . The method of  claim 21 , wherein
 the expeditor runtime component is an extension of the browser.   
     
     
         27 . The method of  claim 21 , wherein
 the widget is dynamically, deployed, installed, and executed during the application session.   
     
     
         28 . A computer hardware system configured to implement a Web application within a client of a local domain, comprising
 a hardware processor programmed to initiate the following executable operations:
 establishing, between a Web server of a Web domain and a browser of the client, an application session for the Web application; 
 serving, from the Web domain to the local domain, a widget and an expeditor runtime component configured to execute the widget; and 
 executing components of the Web application within the Web domain, wherein the widget processes end-user data that is 
 utilized by the Web application within the local domain and 
 isolated from the Web domain. 
   
     
     
         29 . The system of  claim 28 , wherein
 the Web application includes model, view, and controller functionality,   the view and controller functionality are provided by the components of the Web application executing in the Web domain, and   the model functionality is provided by components of the Web application executing in the local domain.   
     
     
         30 . The system of  claim 29 , wherein
 the expeditor runtime component provides the model functionality.   
     
     
         31 . The system of  claim 28 , wherein
 the expeditor runtime component executes in a different physical device from the client, and   a bridge exposes functionality of the expeditor runtime component to the Web application rendered in the browser.   
     
     
         32 . The system of  claim 28 , wherein
 the end-user data is stored within a data store located within the local domain and in a different physical device from the client.   
     
     
         33 . The system of  claim 28 , wherein
 the expeditor runtime component is an extension of the browser.   
     
     
         34 . The system of  claim 28 , wherein
 the widget is dynamically, deployed, installed, and executed during the application session.   
     
     
         35 . A computer program product, comprising
 a hardware storage device having program code for implementing a Web application within a client of a local domain stored therein,   the program code, which when executed by a computer hardware system, causes the computer hardware system to perform:
 establishing, between a Web server of a Web domain and a browser of the client, an application session for the Web application; 
 serving, from the Web domain to the local domain, a widget and an expeditor runtime component configured to execute the widget; and 
 executing components of the Web application within the Web domain, wherein the widget processes end-user data that is 
 utilized by the Web application within the local domain and 
 isolated from the Web domain. 
   
     
     
         36 . The computer program product of  claim 35 , wherein
 the Web application includes model, view, and controller functionality,   the view and controller functionality are provided by the components of the Web application executing in the Web domain, and   the model functionality is provided by components of the Web application executing in the local domain.   
     
     
         37 . The computer program product of  claim 36 , wherein
 the expeditor runtime component provides the model functionality.   
     
     
         38 . The computer program product of  claim 35 , wherein
 the expeditor runtime component executes in a different physical device from the client, and   a bridge exposes functionality of the expeditor runtime component to the Web application rendered in the browser.   
     
     
         39 . The computer program product of  claim 35 , wherein
 the end-user data is stored within a data store located within the local domain and in a different physical device from the client.   
     
     
         40 . The computer program product of  claim 35 , wherein
 the expeditor runtime component is an extension of the browser.