Page Loading Optimization Using Page-Maintained Cache

• US 20120084346A1
• Filed: 10/05/2010
• Published: 04/05/2012
• Est. Priority Date: 10/05/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Mickens, James W.
• Granted Patent: US 9,077,681 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/289 Intermediate processing functionally located close to the data consumer application, e.g. in same machine, in same home or in same sub-network
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Web page loading time may be decreased with the use of a page-maintained storage cache on a client device. In various implementations, a server may receive a request for a web page from a web browser that is on the client device. The server may provide a chunk reassembler to the client device that determines whether any chunks in the web page are already stored on the client device. Subsequently, the server may send one or more chunk of the web page to the client device when the chunk reassembler determines that the one or more chunks of the web page are missing from the client device. The chunk reassembler may then instruct the web browser to assemble the one or more received chunks with the one or more chunks that are stored on the client device into the web page for presentation on the client device.

Claims

1. A computer-readable medium storing computer-executable instructions that, when executed, cause one or more processors to perform operations comprising:

receiving a request for a web page from a web browser that is on a client device;

providing a chunk reassembler to the client device that determines one or more chunks of the web page are already stored on the client device; and

sending at least one chunk of the web page to the client device when the chunk reassembler determines that the at least one chunk of the web page is missing from the client device,

the chunk reassembler instructing the web browser to combine the at least one chunk with the one or more chunks that are stored on the client device into the web page for presentation on the client device.

2. The computer-readable medium of claim 1, further comprising inlining one or more objects into Hypertext Markup Language (HTML) coding of the web page and dividing the web page into chunks prior to or upon receiving the request for the web page, the one or more objects including at least one of a script, a style sheet, or another text-based object.

3. The computer-readable medium of claim 2, further comprising:

assigning a unique identifier to each of the chunks of the web page; and

providing an array of identifiers for the chunks along with the chunk reassembler to the client device,

wherein the chunk reassembler is to determine the one or more chunks of the web page that are stored on the client device by comparing the identifiers in the array to at least one identifier of the one or more chunks stored on the client device.

4. The computer-readable medium of claim 3, wherein the assigning includes assigning a hash of data in a particular chunk to the particular chunk, a globally unique identifier (GUID) to the particular chunk, or a strictly increasing identifier to the particular chunk.

5. The computer-readable medium of claim 2, wherein the dividing of the web page includes dividing the web page into content-delimited chunks using Rabin hash values.

6. The computer-readable medium of claim 2, wherein the dividing of the web page includes dividing the web page into chunks based on a predetermined size limitation for the chunks or a data structure of the web page, or dividing the web page to encapsulate the script or the style sheet in a chunk.

7. The computer-readable medium of claim 1, wherein the chunk reassembler is a JavaScript application.

8. The computer-readable medium of claim 1, wherein the chunk reassembler is to determine the chunks of the web page that are stored in a document object model (DOM) storage of the web browser on the client device.

9. The computer-readable medium of claim 1, wherein the sending includes sending a plurality of chunks to the client device as a delimited HTML string for substring extraction into the plurality of chunks by the chunk reassembler.

10. The computer-readable medium of claim 1, wherein the sending includes sending an annotated version of the web page to the client device when the chunk reassembler determines that none of the chunks of the web page are present on the client device, the annotated version comprising inlined HTML that includes one or more inlined objects and a chunk manifest that is used by the chunk reassembler to parse the inlined HTML into chunks subsequent to a display of the annotated version of the web page on the client device.

12. The method of claim 10, further comprising sending an annotated version of the web page and the chunk reassembler to the client device when the cookie indicates that none of the chunks of the web page are present on the client device, the chunk reassembler to parse inlined HTML of the annotated version into chunks according to a chunk manifest in the annotated version at the client device.

13. The method of claim 12, wherein the inlined HTML comprises one or more inlined objects, and the one or more inlined objects includes at least one of a script, style sheet, or another text-based object.

14. The method of claim 12, wherein the chunk reassembler is to further instruct the web browser to display the inlined HTML in the annotated version of the web page prior to the parse of the inlined HTML.

15. The method of claim 12, wherein the chunk reassembler is to further store the chunks into a document object model (DOM) storage of the web browser.

16. The method of claim 10, wherein the cookie includes a list of chunks of the web page that are stored on the client device.

11. A method, comprising:

receiving a request for a web page and a cookie from a web browser that is on a client device;

sending at least one chunk of the web page and a chunk reassembler to the client device when the cookie indicates that the at least one chunk of the web page is missing from the client device, the chunk reassembler to instruct the web browser to assemble the at least one chunk with one or more chunks that are stored on the client device into the web page for display on the client device; and

sending the chunk reassembler to instruct the web browser to assemble chunks of the web page for presentation on the client device when the cookie indicates that all of the chunks of the web page are stored on the client device.

17. A server, comprising:

one or more processors; and

a memory that includes components that are executable by the one or more processors, the components comprising;

an inline component to inline one or more objects into HTML of a web page, the one or more objects including at least one of a script or a style sheet;

a chunk component to divide the web page into chunks and assign an unique identifier to each chunk; and

a reassembler interface component to send at least one of the chunks and a chunk reassembler to a client device, the chunk reassembler to instruct a web browser on the client device to assemble the at least one chunk with one or more chunks that are stored on the client device into the web page for display on the client device.

18. The server of claim 17, wherein the reassembler interface component is to further determine the one or more chunks of the web page that are stored on the client device by receiving an identifier of each of the one or more chunks via the chunk reassembler and comparing the one or more identifiers to an index of identifiers for the chunks of the web page.

19. The server of claim 17, wherein the reassembler interface component is to further receive a cookie from the web browser, and to send the at least one chunk and the chunk reassembler to the client device when the cookie indicates that the at least one chunk of the web page is missing from the client device.

20. The server of claim 17, wherein the reassembler interface component is to further receive a cookie from the web browser, and to send an annotated version of the web page to the client device when the cookie indicates that none of the chunks of the web page are present on the client device, and wherein the chunk reassembler is to instruct the web browser to display inlined HTML of the annotated version at the client device, and parse the inlined HTML into chunks according to a chunk manifest in the annotated version at the client device.