Independent portlet rendering

• US 8,181,112 B2
• Filed: 05/18/2005
• Issued: 05/15/2012
• Est. Priority Date: 05/21/2004
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Jolley, Christopher, Allamaraju, Subrahmanyam, Pesce, Timmothy
• Primary Examiner(s): Pesin, Boris
• Assistant Examiner(s): HEFFINGTON, JOHN M
• Application Number:
  US11/131,620
• Publication Number:
  US 20060005137A1
• Time in Patent Office: 2,554 Days
• Field of Search: 715/742, 715/203, 715/204, 715/760, 715/739, 715/743, 715/744, 715/745, 715/746, 715/797
• US Class Current: 715/742
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing

Abstract

The rendering of portal pages on can be sped up by allowing individual portlets to be displayed while other portlets of the page are still waiting to finish rendering. Temporary messages can be displayed for the portlets that are still rendering. This temporary content can be replaced by the finished portal rendering for the slow rendering portlets. Additionally, a timeout feature for the portlets can be used. The timeout feature allows the rendering of the portlet to be stopped after a certain period of time.

Claims

1. A computer system for implementing a portal page constructed using portlets, comprising:

a computer including a computer readable medium and processor operating thereon;

a server, executing on the computer, operable to present a portal in response to a request from a client;

a plurality of portlets at the server, wherein each portlet is associated with a plurality of properties, and wherein each portlet is rendered in a separate thread;

a plurality of portal configurations that each define which of the plurality of portlets are included in the portal page and include static content and layout elements which define a layout of the portal page;

wherein the server, upon receiving a request from the client to render the portal page, performs the steps of

providing a connection to the client,

determining, for each of the portlets, whether that particular portlet can be rendered independently of other portlets in the portal page, based on a render property associated with that particular portlet, wherein the render property indicates whether that particular portlet can be rendered asynchronously without affecting functionality of that particular portlet or the other portlets in the portal page,

for each portlet that cannot be rendered independently, providing render information to render those portlets, and

for each portlet that can be rendered independently,

if the portlet is ready to be rendered, providing render information to the client to render that portlet, and

if the portlet is not ready to be rendered,

determining whether the portlet includes an associated property that indicates a location of temporary content which can be rendered temporarily, until that portlet is ready to be rendered,

providing information to the client to render the temporary content for the portlet, and

subsequently, when the portlet is ready to be rendered, providing information to render the portlet to the client which uses scripts in the portal page to replace the temporary content.

2. The computer system of claim 1, wherein portlets have a ‘

fast content URI’

property to indicate a URI of content that can temporarily be displayed if the portlet is slow to render.

6. The computer system of claim 1, wherein the server further performs the steps of:

for each portlet that can be rendered independently, if the portlet is not ready to be rendered

checking a timeout property of the portlet; and

if the timeout property value is exceeded by a rendering time of the portlet, ending the rendering of the portlet.

7. The computer system of claim 6, wherein an error message is displayed when the portlet times out.

15. The computer system of claim 1, wherein the render property is set by a developer using an integrated development environment (IDE).

16. The computer system of claim 1, wherein the render property comprises:

a supports rendering independently property that indicates whether that portlet can be rendered independently; and

a render independently property that instructs the server to render that portlet independently of other portlets in the portal page.

3. A method of displaying a portal page constructed using portlets, the method including:

providing a computer including a computer readable medium and processor operating thereon;

providing a server, executing on the computer, operable to present a portal page in response to a request from a client, wherein the server includes

a plurality of portlets at the server, wherein each portlet is associated with a plurality of properties, and wherein each portlet is rendered in a separate thread;

a plurality of portal configurations that each define which of the plurality of portlets are included in the portal page and include static content and layout elements which define a layout of the portal page;

receiving, by the server, a request from the client to render the portal page;

providing, by the server, a connection to the client;

determining, by the server, for each of the portlets, whether that particular portlet can be rendered independently of other portlets in the portal page, based on a render property associated with that particular portlet, wherein the render property indicates whether that particular portlet can be rendered asynchronously without affecting functionality of that particular portlet or the other portlets in the portal page;

for each portlet that cannot be rendered independently, providing, by the server, information to render those portlets; and

for each portlet that can be rendered independently,

if the portlet is ready to be rendered, providing information to the client to render those portlets,

if the portlet is not ready to be rendered,

determining whether the portlet includes an associated property that indicates a location of temporary content which can be rendered temporarily, until that portlet is ready to be rendered,

providing information to the client to render the temporary content for the portlet, and

subsequently, when the portlet is ready to be rendered, providing information to render the portlet to the client which uses scripts in the portal page to replace the temporary content.

4. The method of claim 3, wherein the display of a portal page does not wait for at least one slow rendering portlet but at least one fast rendering portlet is displayed to the user before the at least one slow rendering portlet.

5. The method of claim 3, wherein portlets have a ‘

fast content URI’

property to indicate a URI of content that can temporarily be displayed if the portlet is slow to render.

8. The method of claim 3, further comprising:

for each portlet that can be rendered independently, if the portlet is not ready to be rendered

checking, by the server, a timeout property of the portlet; and

if the timeout property value is exceeded by a rendering time of the portlet, ending the rendering of the portlet.

9. The method of claim 8, wherein an error message is displayed when the portlet times out.

17. The method of claim 3, wherein the render property is set by a developer using an integrated development environment (IDE).

18. The method of claim 3, wherein the render property comprises:

a supports rendering independently property that indicates whether that portlet can be rendered independently; and

a render independently property that instructs the server to render that portlet independently of other portlets in the portal page.

10. A computer system for implementing a portal page constructed using portlets, comprising:

a computer including a computer readable medium and processor operating thereon;

a server executing on the computer, wherein the server is operable to receive requests from clients and provide a portal page in response;

wherein the portal page includes a plurality of portlets and static content arranged according to a portal configuration, and wherein each portlet is associated with a plurality of properties including a render property which indicates whether that portlet can be rendered asynchronously with other portlets in the portal page without affecting functionality of that portlet; and

wherein when a request is received at the server from a client, the server

determines a set of portlets that can be rendered independently based on the render property,

sends render information to the client for the portal page, the set of portlets, the static content, and temporary content for each portlet that cannot be rendered independently, and

subsequently replaces the temporary content for each portlet when those portlets are ready to be rendered.

11. The computer system of claim 10, wherein the server further performs the steps of:

for each portlet that can be rendered independently, if the portlet is not ready to be rendered

checking a timeout property of the portlet; and

if the timeout property value is exceeded by a rendering time of the portlet, ending the rendering of the portlet.

12. The computer system of claim 10, wherein an error message is displayed when the portlet times out.

13. The computer system of claim 10, wherein at least one fast rendering portlet is displayed to the user before the at least one slow rendering portlet.

14. The computer system of claim 10, wherein portlets have a ‘

fast content URI’

property to indicate a URI of content that can temporarily be displayed if the portlet is slow to render.

19. The computer system of claim 10, wherein the render property is set by a developer using an integrated development environment (IDE).

20. The computer system of claim 10, wherein the render property comprises:

a supports rendering independently property that indicates whether that portlet can be rendered independently; and

a render independently property that instructs the server to render that portlet independently of other portlets in the portal page.