In-line static and dynamic content delivery

• US 8,073,970 B2
• Filed: 06/30/2009
• Issued: 12/06/2011
• Est. Priority Date: 06/30/2009
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Group Incorporated (GoDaddy, Inc.)
• Inventors: Schwimer, Greg
• Primary Examiner(s): WASEL, MOHAMED A
• Application Number:
  US12/495,603
• Publication Number:
  US 20100332587A1
• Time in Patent Office: 889 Days
• Field of Search: 709201-203, 709/238, 709/241
• US Class Current: 709/241
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

Systems and methods of the present invention provide for returning website content after being requested by a client. A static component may be requested, which may be updated, and a dynamic component may be requested. The combination of static and dynamic website content may be returned to the client.

Claims

1. A method, comprising:

a) receiving, by a router communicatively coupled to a computer network, a request for a website content from a client, said website content comprising a static component and a dynamic component;

b) identifying, by said router, a data center in closest physical proximity to said client, said data center comprising one in a plurality of data centers;

c) locating said static component within a cache server in said data center;

d) requesting, by said cache server, an update to said static component and said dynamic component from a shared hosting server in said data center, wherein said shared hosting server is not said cache server and wherein requesting said dynamic component comprises;

i) locating, in a database, personalized information for a user who sent the request, wherein the personalized information is determined from a login or behavior patterns, stored in the database, for the user;

ii) responsive to locating said personalized information, using a scripting language running processes and calculations on said personalized information, to determine the personalized information to be displayed as part of the dynamic content; and

e) returning, by said cache server, said website content to said client.

2. The method of claim 1 wherein said network is a content delivery network.

3. The method of claim 1 wherein said cache server comprises an edge server, wherein said edge server establishes said data center as a regional distribution point based on physical proximity to said client.

4. The method of claim 1 wherein said cache server comprises a web server component used to return said website content.

5. The method of claim 1 wherein said static component comprises streaming content.

6. The method of claim 1 wherein said cache server comprises additional caching layers.

7. The method of claim 1 further comprising the step of determining, by said cache server, whether said static component is contained within a local cache repository communicatively coupled to said cache server.

8. The method of claim 7 wherein said shared hosting server comprises an origin server.

9. The method of claim 8 further comprising the step of requesting, by said cache server, updates to said static component via a header request for a cacheable content from said origin server.

10. The method of claim 8 further comprising the step of determining, by said origin server, updates required for said static component.

11. The method of claim 9 further comprising the step of updating said local cache repository with said cacheable content.

12. The method of claim 8 further comprising the step of identifying said dynamic component to be fetched from said origin server.

13. The method of claim 12 wherein said dynamic component is determined to be incapable of being cached.

14. The method of claim 8 further comprising the step of locating in a database, by said origin server, a stored content used in said dynamic component, wherein said stored content is located in a storage subsystem communicatively coupled to said origin server.

15. The method of claim 14 further comprising the step of processing, by said origin server, said stored content, wherein said processing comprises:

i) analyzing said stored content; and

ii) determining whether and which said stored content should be displayed as part of said dynamic content.

16. The method of claim 8 further comprising the step of processing, by said origin server, a requested SSL certificate.

17. The method of claim 15 further comprising the step of returning said dynamic component to said cache server after processing said stored content.

18. A system, comprising:

a) a client communicatively coupled to a computer network for requesting a website content over said computer network, said website content comprising a static component and a dynamic component;

b) a router communicatively coupled to said computer network for receiving a request for said website content from said client;

c) a plurality of data centers communicatively coupled to said computer network having one data center in closest physical proximity to said client;

d) a cache server hosted in said closest data center that locates said static component within said cache server and that returns said website content to said client;

e) a shared hosting server hosted in said closest data center, said shared hosting server receiving a request from said cache server for said dynamic component and an update to said static component, wherein said shared hosting server is not said cache server;

f) a database configured to locate personalized information for a user who sent the request, wherein the personalized information is determined from a login or behavior patterns, stored in the database, for the user; and

g) a scripting language configured, responsive to locating said personalized information, to run processes and calculations on said personalized information to determine the personalized information to be displayed as part of the dynamic content.