Cross-domain communication

• US 8,689,099 B1
• Filed: 12/23/2010
• Issued: 04/01/2014
• Est. Priority Date: 12/23/2010
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Shalla, Zachary M., Hanni, Jeremy B., Lee, Homan, Thrane, Lon
• Primary Examiner(s): HUYNH, THU V
• Application Number:
  US12/978,116
• Time in Patent Office: 1,195 Days
• Field of Search: 715/240, 715/234, 715/205, 715/200, 715/255
• US Class Current: 715/234
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Disclosed are various embodiments for performing cross-domain communication using messenger frames. One or more messenger frames are dynamically generated in response to determining that a message is to be sent from a first frame in one domain to a second frame in another domain in a client. The message is sent from the first frame to the second frame by embedding the message in addresses of the messenger frames. Code executing in the first frame and code executing in the second frame are restricted from direct communication in the client.

Claims

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

code that determines that a message is to be sent from code executing in a first network page frame to code executing in a second network page frame, wherein the first network page frame is from a first network site, the second network page frame is from a second network site, and the first network page frame and the second network page frame are configured to be rendered together as a network page;

code that determines whether a first domain of the first network site differs from a second domain of the second network site in response to determining that the message is to be sent from the code executing in the first network page frame to the code executing in the second network page frame;

code that sends the message to the code executing in the second network page frame by modifying a document object model (DOM) of the second network page frame to include the message when the first domain is determined not to differ from the second domain; and

code that, when the first domain is determined to differ from the second domain;

dynamically generates a plurality of messenger frames in the second domain;

encodes the message using a uniform resource locator (URL) compliant encoding;

sends the message from the code executing in first network page frame to the code executing in second network page frame by splitting the message into a plurality of message segments based at least in part on a length of the message and embedding individual ones of the plurality of message segments in a query string portion of an address of a corresponding one of the plurality of messenger frames;

wherein individual ones of the plurality of messenger frames corresponds to a respective iframe element in another DOM of the first network page frame; and

wherein the code executing in the first network page frame and the code executing in the second network page frame are restricted from direct communication when the first domain is determined to differ from the second domain.

2. A method, comprising:

determining, via one or more client computing devices, that a message is to be sent from code executing in a first network page frame to code executing in a second network page frame, wherein the first network page frame is from a first network site, the second network page frame is from a second network site, and the first network page frame and the second network page frame are configured to be rendered together as a network page;

determining, via at least one of the one or more client computing devices, whether a first domain of the first network site differs from a second domain of the second network site in response to determining that the message is to be sent from the code executing in the first network page frame to the code executing in the second network page frame;

sending the message to the second network page frame by modifying a document object model (DOM) of the second network page frame to include the message when the first domain is determined not to differ from the second domain; and

when the first domain is determined to differ from the second domain;

dynamically generating, via at least one of the one or more client computing devices, at least one messenger frame in the second domain;

encoding, via at least one of the one or more client computing devices, the message using a uniform resource locator (URL) compliant encoding;

sending, via at least one of the one or more client computing devices, the message from the code executing in first network page frame to the code executing in second network page frame by embedding the message in an address of the at least one messenger frame; and

wherein the code executing in the first network page frame and the code executing in the second network page frame are restricted from direct communication in the one or more client computing devices when the first domain is determined to differ from the second domain.

3. The method of claim 2, wherein the first network site is hosted by a first server, the second network site is hosted by a second server, and the first server and the second server are controlled by different entities.

4. The method of claim 2, wherein the second network page frame corresponds to an iframe element within another document object model (DOM) of the first network page frame.

5. The method of claim 2, wherein the first network page frame corresponds to an iframe element within the document object model (DOM) of the second network page frame.

6. The method of claim 2, wherein the URL compliant encoding includes a Base64 encoding.

7. The method of claim 2, wherein sending the message when the first domain is determined to differ from the second domain further comprises:

determining, via at least one of the one or more client computing devices, whether the message exceeds a maximum encoded message length;

splitting, via at least one of the one or more client computing devices, the message into a plurality of message segments when the message exceeds the maximum encoded message length; and

embedding, via at least one of the one or more client computing devices, individual ones of the plurality of message segments into the address of a corresponding one of the at least one messenger frame.

8. The method of claim 7, wherein dynamically generating the at least one message frame further comprises determining, via at least one of the one or more client computing devices, a quantity of messenger frames to be dynamically generated based at least in part on the maximum encoded message length and the message.

9. The method of claim 7, wherein determining whether the message exceeds the maximum encoded message length further comprises determining, via at least one of the one or more client computing devices, the maximum encoded message length based at least in part on a browser application that is rendering the network page.

10. The method of claim 2, wherein the message includes a plurality of arguments defined in an application programming interface (API) supported by the code executing in the first network page frame and the code executing in the second network page frame.

11. The method of claim 2, wherein the at least one messenger frame corresponds to at least one hidden iframe element in another DOM of the first network page frame.

12. The method of claim 2, further comprising, in response to determining that the first domain differs from the second domain, sending, via at least one of the one or more client computing devices, a callback message from the code executing in the second network page frame to the code executing in the first network page frame using the at least one messenger frame in response to the message.

13. 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 receives a request for a network page frame from a client;

logic that sends the network page frame and code that updates the network page frame to the client, wherein the code that updates the network page frame includes;

code that determines whether a first domain of the network page frame differs from a second domain of another network page frame in response to determining that a message is to be sent from the network page frame to the another network page frame, wherein the network page frame and the another network page frame are configured to be rendered together as a network page;

code that modifies a document object model (DOM) of the another network page to include the message to be sent from the network page frame to the another network page frame when the first domain is determined not to differ from the second domain; and

code that, when the first domain is determined to differ from the second domain;

generates a plurality of messenger frames in the second domain;

divides the message into a plurality of message segments based at least in part on a maximum length of an address field;

encodes the message using a uniform resource locator (URL) compliant encoding before dividing the message into the plurality of message segments; and

sends individual ones of the plurality of message segments to the another network page frame in the second domain using a corresponding messenger frame from the plurality of messenger frames, wherein the address field of the corresponding messenger frame is set to include one of the plurality of message segments; and

wherein the code that updates the network page frame is restricted from direct communication with the another network page frame when the first domain of the network page frame is determined to differ from the second domain of the another network page frame.

14. The system of claim 13, wherein the network page frame includes the another network page frame as an iframe element.

15. The system of claim 13, wherein the network page frame includes the corresponding messenger frame as a hidden iframe element.

16. The system of claim 13, wherein the code that updates the network page frame further includes code that dynamically generates the corresponding messenger frame in another DOM of the network page frame.

17. The system of claim 13, wherein the code that updates the network page frame further includes code that, when the first domain is determined to differ from the second domain, receives the corresponding messenger frame from a pool of available messenger frames.

18. The system of claim 13, wherein the code that updates the network page frame further includes code that when the first domain is determined to differ from the second domain, obtains another message from the another network page frame by way of at least one messenger frame.

19. The system of claim 13, wherein the code that updates the network page frame further includes code that when the first domain is determined to differ from the second domain, identifies the maximum length of the address field according to a browser application executing in the client.

20. 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 receives a request for a network page frame from a client;

logic that sends the network page frame and code that updates the network page frame to the client, wherein the code that updates the network page frame includes;

code that determines whether a first domain of the network page frame differs from a second domain in another network page frame in response to determining that a message is to be sent from the network page frame to the another network page frame, wherein the network page frame and the another network page frame are configured to be rendered together as a network page;

code that modifies a document object model (DOM) of the another network page to include the message to be sent from the network page frame to the another network page frame when the first domain is determined not to differ from the second domain; and

code that, when the first domain is determined to differ from the second domain;

generates at least one messenger frame in the second domain;

generates an encoded message by encoding the message using a uniform resource locator (URL) compliant encoding; and

sends the encoded message to the another network page frame in the second domain using the at least one messenger frame, wherein the encoded message is embedded in an address field of the at least one messenger frame; and

wherein the code that updates the network page frame is restricted from direct communication with the another network page frame when the first domain of the network page frame is determined to differ from the second domain of the another network page frame.

21. The system of claim 20, wherein the network page frame includes the another network page frame as an iframe element.

22. The system of claim 20, wherein the network page frame includes the messenger frame as a hidden iframe element.

23. The system of claim 20, wherein the code that updates the network page frame further includes code that dynamically generates the at least one messenger frame in another DOM of the network page frame.

24. The system of claim 20, wherein the code that updates the network page frame further includes:

code that divides the encoded message into a plurality of message segments based at least in part on a maximum length of the address field; and

wherein the code that sends the encoded message to another network page frame is further configured to send individual ones of the plurality of message segments to the another network page frame in parallel using a corresponding messenger frame in the second domain, wherein the address field of the corresponding messenger frame is set to include one of the plurality of message segments.

25. The system of claim 20, wherein the code that updates the network page frame further includes:

code that divides the encoded message into a plurality of message segments based at least in part on a maximum length of the address field; and

wherein the code that sends the encoded message to another network page frame is further configured to send individual ones of the plurality of message segments to the another network page frame serially using the messenger frame.

26. The system of claim 20, wherein the code that updates the network page frame further includes code that identifies a maximum length of the address field according to a browser application executing in the client.

27. The system of claim 20, wherein the code that updates the network page frame further includes code that determines whether the encoded message exceeds a maximum length of the address field.