EFFICIENT DELIVERY OF WEBPAGES

• US 20150012614A1
• Filed: 09/24/2014
• Published: 01/08/2015
• Est. Priority Date: 03/15/2013
• Status: Abandoned Application

• Current Assignee: Akamai Technologies, Inc.
• Original Assignee: Instart Logic Incorporated (Akamai Technologies, Inc.)
• Inventors: Kolam, Hariharan, Mital, Manav Ratan, Kumar, Rajeev, Venkat, Raghu Batta, Marwah, Abhishek, Kennedy, Brian
• Application Number:
  US14/495,694
• Publication Number:
  US 20150012614A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G06F 16/954 Navigation, e.g. using categorised browsing
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

Abstract

A method of delivering a webpage including dynamic content is disclosed. A request for the webpage directed to a third-party site is received. Likely components corresponding to the webpage is determined with a processor based at least in part on previous responses to similar requests. The determined likely components corresponding to the webpage are sent to a sender of the request. The webpage from the third-party site is received. The remaining components corresponding to the webpage are determined with the processor. The determined remaining components corresponding to the webpage are sent in response to the request.

Claims

1. A system for delivering a webpage, comprising:

a processor configured to;

receive a request for the webpage originally directed to a third-party site;

determine likely components corresponding to the webpage based at least in part on previous responses to one or more previous requests similar to the received request;

send the determined likely components corresponding to the webpage to a sender of the request in response to the request;

receive the webpage from the third-party site;

determine remaining components corresponding to the webpage using the received webpage from the third-party site; and

send the determined remaining components corresponding to the webpage in response to the request; and

a memory coupled to the processor and configured to provide the processor with instructions.

2. The system recited in claim 1, wherein the processor is further configured to send the request to the third-party site.

3. The system recited in claim 1, wherein the sending of the determined likely components corresponding to the webpage is performed prior to the receiving of the webpage from the third-party site.

4. The system recited in claim 1, wherein the sending of the determined likely components corresponding to the webpage comprises sending the components in a webpage file.

5. The system recited in claim 1, wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:

cause the sender of the request, upon receiving at least some of the determined likely components corresponding to the webpage, to be unblocked from at least one task that is blocked by waiting for the webpage.

6. The system recited in claim 1, wherein the memory is further configured to provide the processor with instructions which when executed cause the processor to:

cause the sender of the request, upon receiving at least some of the determined likely components corresponding to the webpage, to begin rendering based at least in part on the determined likely components corresponding to the webpage.

7. The system recited in claim 6, wherein begin rendering comprises one of the following:

loading data into memory or cache, loading code into memory or cache, and downloading dependent resources, wherein the data, the code, and the dependent resources are used for rendering the webpage.

8. The system recited in claim 1, wherein the determined likely components comprises static content.

9. The system recited in claim 1, wherein the determined likely components comprises dynamic content.

10. The system recited in claim 1, wherein the processor is further configured to determine whether rendering the determined likely components of the webpage causes a side-effect or an error.

11. The system recited in claim 10, wherein the processor is further configured to determine whether to correct the side-effect or error.

12. The system recited in claim 11, wherein the processor is further configured to correct the side-effect by sending updates corresponding to the determined likely components based on the webpage received from the third-party site.

13. The system recited in claim 1, wherein the processor is further configured to determine that a Set-Cookie header is not included in the determined likely components and send a JavaScript to the sender to set a cookie based at least in part on the received webpage from the third-party site.

14. The system recited in claim 1, wherein the determined likely components correspond to SWF files, and wherein the processor is further configured to send the components within iframe tags and set an attribute of the iframe to prevent a side-effect of the components being rendered in advance.

15. The system of claim 1, wherein the likely components corresponding to the webpage is a first portion of the webpage and the remaining components corresponding to the webpage is a second portion of the webpage.

16. The system of claim 1, wherein determining the remaining components corresponding to the webpage includes determining whether the determined likely components corresponding to the webpage is included in the received webpage from the third-party site.

17. The system of claim 1, wherein the system is included in a server that belongs to a content delivery network (CDN).

18. The system of claim 1, wherein the determined likely components corresponding to the webpage includes <

head>

tag contents corresponding to the webpage.

19. A method of delivering a webpage, comprising:

receiving a request for the webpage originally directed to a third-party site;

determining with a processor likely components corresponding to the webpage based at least in part on previous responses to one or more previous requests similar to the received request;

sending the determined likely components corresponding to the webpage to a sender of the request in response to the received request;

receiving the webpage from the third-party site;

determining remaining components corresponding to the webpage using the received webpage from the third-party site; and

sending the determined remaining components corresponding to the webpage in response to the request.

20. A computer program product for delivering a webpage, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:

receiving a request for the webpage originally directed to a third-party site;

determining likely components corresponding to the webpage based at least in part on previous responses to one or more previous requests similar to the received request;

sending the determined likely components corresponding to the webpage to a sender of the request in response to the received request;

receiving the webpage from the third-party site;

determining remaining components corresponding to the webpage using the received webpage from the third-party site; and

sending the determined remaining components corresponding to the webpage in response to the request.