Low-latency, incremental rendering in a content framework
First Claim
1. A method of incrementally rendering content in a content framework, comprising:
- receiving a request for a portal page, wherein one or more portlets provide content for the portal page;
immediately returning a response message containing a first document and a refresh trigger responsive to receiving the request, wherein the first document represents results from portlets which have acquired their content but does not represent results of all portlets;
programmatically generating a mechanism for delivering an updated document responsive to immediately returning the response message containing the first document and the refresh trigger, wherein the updated document further represents results from one or more portlets which had not acquired their content when the first document was returned;
receiving a subsequent request for the portal page, the subsequent request having been automatically sent responsive to receiving the refresh trigger; and
returning a subsequent response comprising the updated document responsive to receiving the subsequent request, the updated document being a subsequent version of the first document and representing results from portlets which have acquired their content thus far and which omits the refresh trigger only if all portlets have now acquired their content.
1 Assignment
0 Petitions
Accused Products
Abstract
Techniques are disclosed for incrementally rendering content in a content framework (such as a portal page provided by a portal system). Upon receiving a request for a portal page, a portal server immediately returns a response including the results from portlets which have acquired their content. If some portlets have not yet finished, subsequent content is delivered at a later time through use of one of several alternative programmatically-generated mechanisms. Capabilities of existing browsers are leveraged for several embodiments, including use of refresh headers, multipart MIME (“Multi-purpose Internet Mail Extensions”) types, and portal pages structured using frames.
88 Citations
28 Claims
-
1. A method of incrementally rendering content in a content framework, comprising:
-
receiving a request for a portal page, wherein one or more portlets provide content for the portal page; immediately returning a response message containing a first document and a refresh trigger responsive to receiving the request, wherein the first document represents results from portlets which have acquired their content but does not represent results of all portlets; programmatically generating a mechanism for delivering an updated document responsive to immediately returning the response message containing the first document and the refresh trigger, wherein the updated document further represents results from one or more portlets which had not acquired their content when the first document was returned; receiving a subsequent request for the portal page, the subsequent request having been automatically sent responsive to receiving the refresh trigger; and returning a subsequent response comprising the updated document responsive to receiving the subsequent request, the updated document being a subsequent version of the first document and representing results from portlets which have acquired their content thus far and which omits the refresh trigger only if all portlets have now acquired their content. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
-
22. A method of incrementally rendering content in a content framework, comprising:
-
receiving a request for a portal page, wherein one or more portlets provide content for the portal page; immediately returning a response message containing a first document and a refresh trigger responsive to receiving the request, wherein the first document represents results from portlets which have acquired their content but does not represent results of all portlets; and automatically delivering an updated document responsive to immediately returning the response message containing the first document and the refresh trigger, wherein the updated document further represents results from one or more portlets which had not acquired their content when the first document was returned, and wherein automatically delivering the updated document comprises; receiving a subsequent request for the portal page, the subsequent request having been automatically sent responsive to receiving the refresh trigger; and returning a subsequent response comprising the updated document responsive to receiving the subsequent request, the updated document being a subsequent version of the first document and representing results from portlets which have acquired their content thus far and which omits the refresh trigger only if all portlets have now acquired their content.
-
-
23. A method of incrementally rendering content in a content framework, comprising:
-
receiving a request for a portal page frame, wherein one or more portlets provide content for the portal page frame; immediately returning a response message containing a first mini-document and a refresh header responsive to receiving the request, wherein the first mini-document represents results from portlets which have acquired their content but does not represent results of all portlets; and programmatically generating a mechanism for delivering an updated mini-document responsive to immediately returning the response message containing the first mini-document and the refresh header, wherein the updated mini-document further represents results from one or more portlets which had not acquired their content when the first mini-document was returned; receiving a subsequent request for the portal page frame, the subsequent request having been automatically sent responsive to receiving the refresh header; and returning a subsequent response comprising the updated mini-document responsive to receiving the subsequent request, the updated mini-document being a subsequent version of the first mini-document and representing results from portlets which have acquired their content thus far and which omits the refresh header only if all portlets have now acquired their content. - View Dependent Claims (24, 25, 26, 27, 28)
-
Specification