Static Server Pages
Static Server Page (USP) components generate a complete web page every time they are activated. This makes them useful for relatively static web pages or a thin-client architecture in which all processing is done on the server. They can also be used for RESTful applications or file upload functionality.
The static server page has the following characteristics:
- Full page updating at runtime. Incremental updating is not supported.
- Support for HTTP requests, so they can be used to support file downloads.
- Proprietary XHTML tags represent Uniface data structures in the layout.
- Widgets are implemented as HTML.
- The only interactive trigger is the detail trigger on the Button widget.
- Syntax checking is performed in the browser by a Java applet.
- USPs cannot be used for mobile apps.
All interaction passes through the server and communication is synchronous. Data is sent to the server, the server responds, and the entire HTML page is reloaded with the response. For more information, see Processing Requests and Responses for Static Server Pages.
A static server page definition consists of a component definition and the layout definition. Compiling the server page creates a deployable file with the extension .usp. During deployment, the .usp file is used to generate an XHTML page that is sent to the browser.
You can use external layout definitions to deploy the web application, in which case the layout definition must be saved as a .hts file with the same name as the server page.
During deployment, both the .usp file and the .hts file are used to generate the XHTML page. To use external layout definitions, you must use the assignment setting $SEARCH_SKELETON.You can also use multiple layout definition files for generating the XHTML page for thse browser.
