The client side portlet programming model
You can benefit from the portal client side aggregation by using
the client side programming model for portlets.
You can use the client side programming model for writing your
portlets. You can do everything with the client side programming model that
you can do with the server side portlet programming model. Additionally, the
client side programming model has the following advantages:
- Improved user experience by faster response and performance. Portlets
that use the clients side programming model render faster, as the portal does
not re-render the whole page, but only the aspects of the portlet that change.
- The client side programming model allows you to handle changes of the
portlet mode and window state, preferences, and user customization of user
profile locally. This provides a faster response time for the user. A fragment
that contains the customization is later sent to the server and saved.
- The client side portlet programming model works in both client side aggregation
(CSA) and server side aggregation (SSA).
- The use of the CSA architecture for portlets in your portal is optional.
SSA is provided as a fallback option. For example, if the browser does not
support JavaScript, the "old" portal rendering procedure is still available.
- Writing portlets to the client side programming model does not require
deep Java knowledge Such portlets can be written as html code with css style
sheets and javascript. They have few or no JSPs. Example scenarios for writing
client side portlets are:
- A user can add some markup to the portlet view by selecting options in
a form.
- Preference changes that a user makes to the portlet are applied immediately
in the browser view without reloading the whole portlet. The preference change
is later sent to the server and saved.
- Client side user profile access.
- Portlet mode changes are performed entirely on the client. Performance
improves as no server-client round trips are required.
- The portlet can retrieve markup fragments from the server. The user does
not notice this, as the ATOM feed format is hidden by the XMLPortletRequest
implementation, similar to a XMLHttpRequest.
- XSLT and XPath helper functions make it easier to handle XML feeds.
Parent topic: Developing portlets
|
|
|