In a reactive object server, your application is interfaced with application components by means of C++ objects called views. A view maintains the consistency between a structure of inter-related server objects and a component representation of these objects.

A view subscribes to all or part of the Server objects. When these objects are in a logical state of creation, modification, or deletion, each view notifies its associated component representation accordingly. Views are instances of dynamic view types specified by the user at runtime. Dynamic views are high-level services which allow you to start a server as soon as its object model is implemented.

Dynamic-view services provide a generic representation protocol to handle the interactions between view servers and components. Developing a component consists in implementing a bridge between the two classes of the generic representation protocol —IlsRpObject and IlsRepresentation— and the internal component classes.

Moreover, dynamic view services also integrate the communication layer between servers and components. Thus, making a linked Server application distributed requires only a few modifications in the main function of the executable and in the make file.

Writing a Server application involves three basic development steps:

To complete the third step, you can use the Rogue Wave Server/Rogue Wave Views integration. Using Rogue Wave Server Studio allows you to specify dynamic-view types via a graphical interface and associate them with gadgets, thus implementing most of your graphical components without coding.

The components can be either linked to the server or distributed.

Finally, Rogue Wave Server also provides integration with a JavaTM Graphical User Interface by means of the Rogue Wave Server Java Data Sources. Java data sources are a predefined mapping which you can use to interface server obejcts with Swing or Rogue Wave JViews graphical objects.