An Rogue Wave® Server application includes one or more view servers that interact with components by means of views. Such an application can be linked or distributed. With the dynamic-view approach, the distribution layer is embedded in a specific Rogue Wave Server library and remains transparent to the user. Basically, the difference between a linked application and a distributed application is only a matter of choosing a different process initialization to select the communication layer (in most cases, MvTCP or a CORBA Object Request Broker).

A dynamic view server can be executed in multithread mode at several stages of an interaction cycle:

Components must connect to the dynamic view server before opening views. Rogue Wave Server supplies several ways to open a view either directly from the server or from the component.

Interactions between an object server and its components are based on interaction cycles. These cycles use asynchronous transaction services implemented on both sides. Rogue Wave Server provides an API that lets you customize the execution of transactions both on the component side and on the server side.