Optimizing bandwidth usage and improving performance for web page caching

• US 10,277,703 B2
• Filed: 07/22/2015
• Issued: 04/30/2019
• Est. Priority Date: 07/22/2015
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Cuduvalli Ravikanth Rao, Siddharth, Shamanna, Guru Prasad
• Primary Examiner(s): Parry, Chris
• Assistant Examiner(s): Hlaing, Soe M
• Application Number:
  US14/805,718
• Publication Number:
  US 20170026449A1
• Time in Patent Office: 1,378 Days
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: G06Q 30/0277 Online advertisement
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/5682 Policies or rules for updating, deleting or replacing the stored data

Abstract

Improving of bandwidth usage and performance for web page caching. Responsive to a subsequent request for a web page, a server only returns the set of web page portions of the requested web page that are not in a browser cache, have expired, and/or have changed.

Claims

1. A method comprising:

receiving, by a server from a browser, a first request for a first web page, wherein the first webpage comprises a first set of portions;

sending, by a server to a browser, the first web page and a first set of web page metadata, wherein the first set of web page metadata comprises a first set of web page portion definitions, a first set of request dates, a first set of expiration dates, and a first set of caching policies;

receiving, by the server from the browser, a second request for a second web page, wherein the second request comprises a second set of web page metadata, and wherein the second set of web page metadata comprises a second set of web page portion definitions, a second set of request dates, a second set of expiration dates, and a second set of caching policies;

correlating, by the server, the first set of web page metadata to the second set of web page metadata;

determining, by the server, that a first subset of portions of the first web page has changed, based on the second set of web page portion definitions;

determining, by the server, that a second subset of portions of the first web page has not been cached, based on the second set of caching policies;

determining, by the server, that a third subset of portions of the first web page has expired, based on the second set of expiration dates;

creating, by the server, a third set of web page metadata; and

returning, by the server to the browser, the third set of web page metadata and the second subset of portions of the first web page that has not been cached, wherein the third set of web page metadata comprises a third set of web page portion definitions, a third set of request dates, a third set of expiration dates, and a third set of caching policies.

2. The method of claim 1, wherein the first web page and the second web page are web pages on a domain.

3. The method of claim 2, wherein the second web page is the first web page.

4. The method of claim 1, further comprising:

caching the first web page to a cache; and

stitching the second web page, wherein the second web page includes the first subset of the first web page portions that has changed.

5. The method of claim 4, wherein stitching the second web page comprises:

retrieving the first subset of the first web page from the cache; and

combining a set of web page portions associated with the second web page with the first subset of the first web page corresponding to a set of web page portions of the second web page not received in the receiving step.

6. The method of claim 1, wherein creating the third set of web page metadata comprises:

determining, by the server, whether a first portion of the first web page is in a cache for the browser;

responsive to determining that the first portion of the first web page is not in the cache for the browser, creating, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, a caching policy, and a status tag;

responsive to determining that the first portion of the first web page is in the cache for the browser, determining, by the server, whether the first portion of the first web page is cached inline;

responsive to determining that the first portion of the first web page is not cached inline, creating, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, a caching policy, and a status tag; and

responsive to determining that the first portion of the first web page is cached inline, creating, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, an inline caching policy, and a status tag.

7. The method of claim 1, wherein creating the third set of web page metadata comprises:

subsequent to receiving the second request, determining, by the server, whether a first portion of the second web page is in a cache of the browser,

responsive to determining that the first portion of the second web page is not in the cache, determining, by the server, whether the first portion of the second web page is ever cached;

responsive to determining that the first portion of the second web page is never cached, appending, by the server, the first portion of the second web page to a set of content to be returned to the browser;

responsive to determining that the first portion of the second web page is in the cache, determining, by the server, whether the first portion of the second web page has expired or changed; and

responsive to determining that the first portion of the second web page has not expired or changed, updating, by the server, the third set of web page metadata to reflect an updated request date and updated expiration date.

8. A computer system comprising:

one or more computer processors;

one or more computer readable storage media; and

program instructions stored on the one or more computer readable storage media for execution by at least one of the one or more computer processors, the program instructions comprising;

program instructions to receive, by a server from a browser, a first request for a first web page, wherein the first webpage comprises a first set of portions;

program instructions to send, by a server to a browser, the first web page and a first set of web page metadata, wherein the first set of web page metadata comprises a first set of web page portion definitions, a first set of request dates, a first set of expiration dates, and a first set of caching policies;

program instructions to receive, by the server from the browser, a second request for a second web page, wherein the second request comprises a second set of web page metadata, and wherein the second set of web page metadata comprises a second set of web page portion definitions, a second set of request dates, a second set of expiration dates, and a second set of caching policies;

program instructions to correlate, by the server, the first set of web page metadata to the second set of web page metadata;

program instructions to determine that a first subset of portions of the first web page has changed, based on the second set of web page portion definitions;

program instructions to determine that a second subset of portions of the first web page has not been cached, based on the second set of caching policies;

program instructions to determine that a third subset of portions of the first web page has expired, based on the second set of expiration dates;

program instructions to create a third set of web page metadata; and

program instructions to return, by the server to the browser, the third set of web page metadata and the second subset of portions of the first web page that has not been cached, wherein the third set of web page metadata comprises a third set of web page portion definitions, a third set of request dates, a third set of expiration dates, and a third set of caching policies.

9. The computer system of claim 8, wherein the first web page and the second web pages on a domain.

10. The computer system of claim 9, wherein the second web page is the first web page.

11. The computer system of claim 8, further comprising:

program instructions to cache the first web page to a cache; and

program instructions to stitch the second web page, wherein the second web page includes the first subset of the first web page portions that has changed.

12. The computer system of claim 11, wherein the program instructions to stitch the second web page comprise:

retrieving the first subset of the first web page from the cache; and

combining a set of web page portions associated with the second web page with the first subset of the first web page corresponding to a set of web page portions of the second web page not received in the receiving step.

13. The computer system of claim 8, wherein the program instructions to create the third set of web page metadata comprise:

program instructions to determine, by the server, whether a first portion of the first web page is in a cache for the browser;

responsive to determining that the first portion of the first web page is not in the cache for the browser, program instructions to create, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, a caching policy, and a status tag;

responsive to determining that the first portion of the first web page is in the cache for the browser, program instructions to determine, by the server, whether the first portion of the first web page is cached inline;

responsive to determining that the first portion of the first web page is not cached inline, program instructions to create, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, a caching policy, and a status tag; and

responsive to determining that the first portion of the first web page is cached inline, program instructions to create, by the server, a set of metadata for the first portion, wherein the set of metadata for the first portion comprises a web page portion definition, an inline caching policy, and a status tag.

14. The computer system of claim 8, wherein the program instructions to create the third set of web page metadata comprise:

subsequent to receiving the second request, program instructions to determine, by the server, whether a first portion of the second web page is in a cache of the browser,

responsive to determining that the first portion of the second web page is not in the cache, program instructions to determine, by the server, whether the first portion of the second web page is ever cached;

responsive to determining that the first portion of the second web page is never cached, program instructions to append, by the server, the first portion of the second web page to a set of content to be returned to the browser;

responsive to determining that the first portion of the second web page is in the cache, program instructions to determine, by the server, whether the first portion of the second web page has expired or changed; and

responsive to determining that the first portion of the second web page has not expired or changed, program instructions to update, by the server, the third set of web page metadata to reflect an updated request date and updated expiration date.

15. A computer program product comprising:

one or more computer readable storage media; and

program instructions stored on the one or more computer readable storage media, the program instructions comprising;

program instructions to receive, by a server from a browser, a first request for a first web page, wherein the first webpage comprises a first set of portions;

program instructions to send, by a server to a browser, the first web page and a first set of web page metadata, wherein the first set of web page metadata comprises a first set of web page portion definitions, a first set of request dates, a first set of expiration dates, and a first set of caching policies;

program instructions to receive, by the server from the browser, a second request for a second web page, wherein the second request comprises a second set of web page metadata, and wherein the second set of web page metadata comprises a second set of web page portion definitions, a second set of request dates, a second set of expiration dates, and a second set of caching policies;

program instructions to correlate, by the server, the first set of web page metadata to the second set of web page metadata;

program instructions to determine that a first subset of portions of the first web page has changed, based on the second set of web page portion definitions;

program instructions to determine that a second subset of portions of the first web page has not been cached, based on the second set of caching policies;

program instructions to determine that a third subset of portions of the first web page has expired, based on the second set of expiration dates;

program instructions to create a third set of web page metadata; and

program instructions to return, by the server to the browser, the third set of web page metadata and the second subset of portions of the first web page that has not been cached, wherein the third set of web page metadata comprises a third set of web page portion definitions, a third set of request dates, a third set of expiration dates, and a third set of caching policies.