Application models

There are several application patterns that are recommended for use in the managed client platform. One pattern is the browser user interface pattern, which is supported by the Web Application Model. Web applications present their user interface through the use of generated scripting language such as HTML, which is rendered for display by a browser.

Another pattern is to build a graphical user interface using Eclipse, to aggregate display components into views, and views into perspectives. Applications will be defined using extension points to define the actions, views, and perspective that provide the user interface. This pattern is the rich client user interface pattern, which is supported by the Rich Client Application Model.

For Lotus^® Expeditor Client for Desktop, there are additional application patterns. The portlet pattern is supported by the Portlet Application Model. This pattern is based on JSR 168.

Another pattern is the Composite Application pattern, which is supported by the Composite Application Model. In this model, multiple applications cooperate by using inter-component communications. For example, you can use the Property Broker to communicate among portlets and/or Eclipse applications running in the same client process. Or, you can use the micro broker to communicate among applications running in the same or different processes.