Distributed network page generation

• US 8,930,443 B1
• Filed: 03/18/2011
• Issued: 01/06/2015
• Est. Priority Date: 03/19/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Boynes, Jeremy, Warner, William Haywood, Vickers, Shaun M., Yasen, Wisam Z.
• Primary Examiner(s): Bates, Kevin
• Assistant Examiner(s): Rahman, SM
• Application Number:
  US13/051,383
• Time in Patent Office: 1,390 Days
• Field of Search: 709/203
• US Class Current: 709/203
• 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/01 Protocols
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70

Abstract

Disclosed are various embodiments for distributed generation of network pages from portions of network pages. A first request for a network page is obtained. A second request for a network page portion is sent to a server application. The second request includes a protocol header that specifies a base uniform resource locator (URL). The network page portion is obtained from the server application. The network page portion is based at least in part on the base URL. The network page is generated from the network page portion and other data.

Claims

1. A non-transitory computer-readable medium embodying a program executable in a computing device, the program comprising:

code that obtains a first hypertext transfer protocol (HTTP) request for a network page from a client;

code that identifies a plurality of network page portions of the network page and requests corresponding configurations for individual ones of the plurality of network page portions from a configuration application;

code that sends a second HTTP request for a first one of the identified network page portions to a first server application, the second HTTP request including a first configuration of the corresponding configurations and a non-standard HTTP header that specifies a base uniform resource locator (URL) identifying the network page;

code that obtains the first one of the identified network page portions from the first server application, wherein the first one of the identified network page portions is based at least in part on the base URL and the first configuration;

code that sends a third HTTP request for a second one of the identified network page portions to a second server application, the third HTTP request including a second configuration and the non-standard HTTP header that specifies the base URL;

code that obtains the second one of the identified network page portions from the second server application, wherein the second one of the identified network page portions is based at least in part on the base URL;

code that generates the network page from the first one of the identified network page portions, the second one of the identified network page portions, and other data; and

code that sends the network page to the client in response to the first HTTP request.

2. The non-transitory computer-readable medium of claim 1, wherein the first HTTP request includes a first cookie associated with the first server application and a second cookie associated with the second server application, wherein each cookie includes a respective publisher identification, the second HTTP request includes the first cookie without the respective publisher identification, and the third HTTP request includes the second cookie without the respective publisher identification.

3. The non-transitory computer-readable medium of claim 2, wherein the first cookie corresponds to a first session identification associated with the first server application, and the second cookie corresponds to a second session identification associated with the second server application.

4. A system, comprising:

at least one computing device; and

a network page generation application executable in the at least one computing device, the network page generation application comprising;

logic that obtains a first request for a network page;

logic that identifies a network page portion of the network page and obtains configuration information for the network page portion from a configuration application;

logic that sends a second request for the network page portion to a server application, the second request including a first protocol header and a second protocol header, wherein;

the first protocol header specifies a base uniform resource locator (URL) and the configuration information for the network page portion, wherein the base URL identifies the network page,

the second protocol header identifies a base path specifying a network location of the network page portion, wherein the network page portion includes a callback that incorporates the base path;

logic that obtains a third request from a client, the third request being generated by the callback in the network page portion, the third request specifying the base path within a requested URL;

logic that identifies the server application according to the base path;

logic that obtains the network page portion from the server application, wherein the network page portion is based at least in part on the base URL and the configuration information; and

logic that generates the network page from the network page portion and other data.

5. The system of claim 4, wherein the first request includes a cookie having an identifier of the server application, and the second request includes the cookie with the identifier of the server application removed.

6. The system of claim 5, wherein the first request includes another cookie having a different identifier, and the second request does not include the another cookie.

7. The system of claim 4, wherein the network page generation application further comprises:

logic that obtains a session identifier from a session establishment application associated with the server application; and

logic that provides the session identifier within the second request.

8. The system of claim 7, wherein the network page generation application further comprises logic that returns a cookie including the session identifier with the network page portion.

9. The system of claim 4, wherein the network page generation application further comprises:

logic that obtains configuration data regarding the network page portion;

logic that obtains definition data regarding the network page portion based at least in part on the configuration data; and

logic that generates a request URL for the second request according to an endpoint specified in the configuration data, the request URL including a plurality of parameters determined at least in part from the definition data.

10. The system of claim 9, wherein the configuration application is executable in the at least one computing device, the configuration application comprising:

logic that obtains a configuration request from an administrative user to specify the endpoint in the configuration data; and

logic that modifies the configuration data to specify the endpoint in response to the configuration request.

11. The system of claim 4, wherein the network page generation application further comprises:

logic that sends a fourth request for data relating to the network page portion to the server application in response to the third request;

logic that obtains the data relating to the network page portion from the server application; and

logic that sends the data relating to the network page portion to the client.

12. The system of claim 4, wherein the second request includes another protocol header that specifies a document object model (DOM) identifier that is unique within a DOM of the network page, and the network page portion includes at least one resource that references the DOM identifier.

13. The system of claim 4, wherein the second request includes another protocol header that specifies a document type, and the network page portion conforms to the document type.

14. The system of claim 4, further comprising a network page server application executable in the at least one computing device, the network page server application comprising:

logic that obtains the first request from a client; and

logic that sends the network page to the client in response to the first request.

15. The system of claim 4, wherein the first request and the second request are hypertext transfer protocol (HTTP) requests.

16. The system of claim 15, wherein the protocol header is an HTTP non-standard header.

17. A method, comprising:

obtaining, in at least one computing device, a first request for a network page from a client;

sending, in the at least one computing device, a second request for a network page portion to a server application, the second request including a protocol header that specifies a base path identifying a location of the network page portion;

obtaining, in the at least one computing device, the network page portion from the server application, wherein the base path is included in at least one client-side callback embedded in the network page portion;

obtaining, in the at least one computing device, a third request from the client, the third request being generated by the at least one client-side callback and specifying the base path within a requested uniform resource locator (URL);

identifying, in the at least one computing device, the server application according to the base path;

generating, in the at least one computing device, the network page from the network page portion and other data; and

sending, in the at least one computing device, the network page to the client in response to the first request.

18. The method of claim 17, further comprising:

sending, in the at least one computing device, a fourth request for data relating to the network page portion to the server application in response to the third request;

obtaining, in the at least one computing device, the data relating to the network page portion from the server application; and

sending, in the at least one computing device, the data relating to the network page portion to the client.

19. The method of claim 17, further comprising:

determining, in the at least one computing device, whether the network page portion is cached; and

obtaining, in the at least one computing device, the network page portion from a cache instead of the server application when the network page portion is cached.

20. The method of claim 17, wherein the second request includes another protocol header that specifies a base uniform resource locator (URL), and the network page portion is based at least in part on the base URL.

21. The method of claim 17, wherein the second request includes another protocol header that specifies a document object model (DOM) identifier that is unique within a DOM of the network page, and the network page portion includes at least one resource that references the DOM identifier.

22. The method of claim 17, further comprising:

obtaining, in the at least one computing device, configuration data regarding the network page portion;

obtaining, in the at least one computing device, definition data regarding the network page portion based at least in part on the configuration data; and

generating, in the at least one computing device, a request uniform resource locator (URL) for the second request according to an endpoint specified in the configuration data, the request URL including a plurality of parameters determined at least in part from the definition data.