Kbase P25821: Dynamics. Client Support.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
26/05/2003 |
|
Status: Unverified
GOAL:
Dynamics. Client Support.
FACT(s) (Environment):
Dynamics 2.0A
FIX:
The first commercial release of Dynamics, called Version 1.1, supports 4GL clients, including the standard Progress runtime client and the new Progress WebClient·. The WebClient allows application users to download a fully functional no-cost Progress client executable over the Internet and run the client part of your application from anywhere in the world without the need to distribute or maintain Progress runtime installations or the application itself. In the near future, Dynamics will support native web browser-based access to the same abstract application definition. This support will allow part or all of an application to be rendered in a browser without the need for a Progress runtime client at all, still accessing the same back-end business logic on server machines connected to the database. Other client platforms (such as handheld display devices or platforms not yet anticipated) can be driven from the same data definition, without change to the business logic or basic application definition, because most of the client part of the application is data, not procedural code.
Dynamics is designed to run in a distributed environment, with the visual portion of the application running in either a 4GL client session or some other client type, without a local database connection. Business logic runs on one or on many Progress AppServer· sessions where the repository database and the application database can be located, maximizing efficiency of access to the database. Access to the AppServer is always stateless, so that a small pool of AppServer sessions can support a large number of clients.
To support this stateless AppServer access, Dynamics includes a number of Manager procedures to handle various aspects of the application and its environment. Each of these procedures runs as both a client-side manager and a server-side manager. The server-side manager maintains one or more repository database tables on the server, and provides data to client sessions as needed. Data is cached on the client for maximum efficiency, and returned to the server when necessary to allow the repository database to provide persistent storage for all data relating to the running of the application. In the future, a Web manager will provide access to the same managers and data from a WebSpeed® application running in a web browser.