Develop a Uniface Web Application
When developing a web application you need to follow the Uniface development paradigm of model, construct, build, test, and deploy. Web applications are stateless, so you need to consider how you will manage state, how to maximize performance, and protect security.
- Start by creating modeled entities to model
the application data and default behavior. These can then be reused in the components. For more information, see Define a Modeled Entity.
Keep the following points in mind:
- Some triggers that you can specify in modeled entities and fields are not available in web applications, so code in these triggers has no effect. For more information, see Triggers in Dynamic Server Pages and Triggers in Static Server Pages .
- Field syntax checking is done in the browser. It is not handled directly by Uniface. For more information, see Syntax Checking in Web Applications.
- Locking and validation behave differently from client/server applications. For more information, see Locking in Web Applications and Data Validation in Web Applications.
- Construct components for the user interface
and business logic. For more information, see Construct a Component.
You can use dynamic server pages and static server pages for the user interface, and services to handle server-side business logic. In dynamic server pages, you can reduce network traffic by performing some logic in the browser.
- When scripting web application components,
you need to pay particular attention to locking, validation, and syntax checking, state management
and authentication. For more information, see Scripting in Server Pages .
See also:
- Compile, test, and debug the application. For more information, see Debugging in a Web Environment.
- Optionally define a customized application server to handle user and request authentication and verification. The default Uniface Server does not do this. For more information, see Application Shells for Servers and Define an Application Server Shell.
- Deploy and configure the application. For more information, see Deploying Uniface Web Applications.