Browse Prior Art Database

Optimizing and Minimizing Portlet Round Trips to a Portal Server

IP.com Disclosure Number: IPCOM000015059D
Original Publication Date: 2001-Sep-01
Included in the Prior Art Database: 2003-Jun-20
Document File: 4 page(s) / 72K

Publishing Venue

IBM

Abstract

Disclosed is a method and process for minimizing the client to portal server requests made in a functioning portal. These requests are minimized on portlet requests where help information is displayed. This invention teaches a method and process for minimizing the flows to a Websphere Portal Server. This optimization can be realized and adopted in other web servers, but WPS is used in the preferred embodiment.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 53% of the total text.

Page 1 of 4

Optimizing and Minimizing Portlet Round Trips to a Portal Server

   Disclosed is a method and process for minimizing the client to portal server requests made in a functioning portal. These requests are minimized on portlet requests where help information is displayed. This invention teaches a method and process for minimizing the flows to a Websphere Portal Server. This optimization can be realized and adopted in other web servers, but WPS is used in the preferred embodiment.

   Portal Servers are one of the most popular web offerings in today's Internet. A portal server serves up web pages to a community of users. Each user is presented with a web page with a selection of portlets. Each portlet is a mini application that displays custom content for the user. Each user's page may be different, with a different selection of portlets, and within each portlet user customized content.

   For example, one user may have a stock quotes portlet, another user may not. The user who has this portlet selects a list of stock symbols and the portlet then displays the latest quotes for those symbols.

Figure 1 - Sample Portal Page

In the current art, each time a portlet interacts with a portlet this generates a URI back to portal server. This URI is typically encoded with state information, actions, or other data from the portlet, that is to be processed by the portal server. The portal then responds back to the client with a new stream of markup to display the new updated portal page. This process is markup independent, and works the same way whether the markup is HTML, XML, WML, CHTML or some other markup.

1

[This page contains 2 pictures or other non-text objects]

Page 2 of 4

Optimizing and minimizing the flows to and from the portal server enhances the performance characteristics of the portal server.

Each portlet in a WPS Portal Server has four display modes: View, Help, Customize, Configure. The user of a portlet can invoke only the first three modes: View, Help, and Customize.

The optimization is related to a portlet's view and help modes. In the current portlet art every time the portlet user presses the information button on the title bar of the portlet, the button press event is sent to the portal server, and the portal server responds with the markup for the help page, which is presented in the portlets frame and temporarily replaces the contents of the view mode. When the user clicks the information button again, the portlets view mode is returned to view mode by again sending the button event to the portal and the portal calling the portlet to obtain the new markup.

The portlet help content is typically static in nature, so a...