Client Implementation 

The graphic below gives an outline of the concept of the client implementation:

Depending on the rendering device that is selected, the central part of the Web Dynpro runtime works together with a certain client implementation. In the case of a browser, this is server-side rendering (SSR). SSR then takes over the task of communicating with the client device. When eCATT is used (see also Creating Test Cases with CATT and Extended CATT), the client implementation is used in its XML version, and the data and the layout are transferred separately (unlike the browser).

View elements are in user interface element libraries, see also Web User Interfaces.

With the Web Dynpro for ABAP, a browser is always used as the rendering device. Data, events and layout information are converted on the server into HTML and JavaScript and transferred together. In the case of the browser, this is usually done mostly on the server; the whole layout is placed on the server, for example. The browser itself does not take on many tasks. For example, it is responsible for ensuring that a tray or the nodes of a tree on the client can be expanded or collapsed.

When they are called by the Web Dynpro runtime, specific adapter techniques are used to convert data and events as part of the request response cycle into the browser’s format, HTML and JavaScript or XML. Conversely, these data are then converted into ABAP Objects data structures.