Configuring Siebel Open UI > Architecture of Siebel Open UI > About the Siebel Open UI Development Architecture >

Differences in the Server Architecture Between High Interactivity and Siebel Open UI

Figure 13 compares the server architecture between high interactivity and Siebel Open UI.

Figure 13. Comparing Server Architecture Between High Interactivity and Siebel Open UI

Explanation of Callouts

This comparison between the architecture that high interactivity uses and that Siebel Open UI uses includes the following items:

1. Rendering customization in high interactivity requires you to use a SWEFrame customization at the applet level.
2. Rendering customization in Siebel Open UI allows you to use SWEFrame customization, an equivalent customization, or to customize the physical renderer independently at any level of the object hierarchy, including at the subapplet level for an applet control.
3. High interactivity always starts rendering at the view level. It uses predefined code in the user interface hierarchy, from a request processing perspective.
4. Siebel Open UI uses objects, so rendering can occur at the screen, view, applet, or control level.