Page History

...

• A WAM Component is a type of RDMLX Component. It can instantiate and invoke other non-visual RDMLX Components.
• Each WEBROUTINE in a WAM can be invoked from the browser. It can also be exposed via a Service Name mechanism.
• A WAM supports the concept of a Web session. The session key to identify the Web session is stored in the browser.
• When a WEBROUTINE request is made from a browser (or other type of client device), a WAM Component is created, its requested WEBROUTINE is executed, and the WAM Component is destroyed. This process reduces the server resource usage and ensures maximum scalability.
• Since WAM execution maintains state on a per-request basis, a configurable pre-defined number of Web jobs can service many Web sessions and the requests can be shared amongst multiple application server machines.
• Any data, (i.e. fields, lists, other Component state), is destroyed upon WEBROUTINE termination and is not available on subsequent request.
• Any field or list marked with OPTIONS(*PERSIST) to declare it as session state are not destroyed but stored in a database on the server. It is possible to change this data in one WEBROUTINE request and have it available for subsequent WEBROUTINE requests.
• If no requests have been made for a session within a specified timeout period, the session is deemed expired. Any further requests from the same session will result in a SessionInvalid event being triggered. An event handler for this event can be used to handle session.