Method and apparatus for cross-domain communication using designated response processing page

• US 8,090,763 B2
• Filed: 08/18/2009
• Issued: 01/03/2012
• Est. Priority Date: 08/25/2008
• Status: Expired

• Current Assignee: Alibaba Group Holding Ltd.
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Li, Zhanyuan
• Primary Examiner(s): Patel, Haresh N
• Application Number:
  US12/583,362
• Publication Number:
  US 20100049782A1
• Time in Patent Office: 868 Days
• Field of Search: 709200-203, 709217-228, 715/231, 715/234, 715/765
• US Class Current: 709/202
• 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 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46

Abstract

Cross-domain communication between a sender domain and a receiver domain includes: receiving, in the receiver domain, a data request from the sender domain, the data request being directed to a designated request processing page in the receiver domain; processing the data request to generate a response; and sending the response to the sender domain, the response being directed to a designated response processing page in the sender domain. Alternatively, cross-domain communication includes receiving, in the receiver domain, a data request from the sender domain, the data request being directed to a designated request processing page in the receiver domain; processing the data request to generate a response; and sending the response to the sender domain, the response being directed to a designated response processing page in the sender domain.

Claims

1. A sender system for cross-domain communication between a sender domain and a receiver domain that is different from the sender domain, comprising:

a hardware processor configured to;

send a data request from an originating webpage deployed in the sender domain to the receiver domain, the data request being directed to a designated request processing page in the receiver domain, wherein sending the data request from the sender domain to the receiver domain includes opening a hidden page and using the hidden page to open the designated response processing page and to send a request command and associated request data via the hidden page, wherein opening the hidden page includes opening an invisible new window or an invisible iframe;

receive a response from the receiver domain, the response including requested data and being directed to a designated response processing page in the sender domain, wherein the designated response processing page deployed in the sender domain is a different webpage from the originating webpage deployed in the sender domain; and

process the response; and

a memory coupled to the hardware processor, configured to provide the hardware processor with instructions.

2. The system of claim 1, wherein the data request is sent in response to a client action from a browser to an originating webpage in the sender domain.

3. The system of claim 1, wherein the designated request processing page is deployed in the receiver domain and the designated response processing page is deployed in the sender domain prior to the cross-domain communication.

4. The system of claim 1, wherein the data request includes a request command and associated request data that are sent via a Hypertext Transfer Protocol (HTTP) GET command.

5. The system of claim 1, wherein:

the data request includes a request command and associated request data;

the request command is sent as a fragment identifier attached to a uniform resource locator (URL); and

the associated data are transferred as a name property of a window object.

6. The system of claim 1, wherein:

the data request includes a request command and associated request data;

the request command and the associated request data are sent as a fragment identifier attached to a URL.

7. The system of claim 1, wherein request is transferred as a string in JSON format.

8. The system of claim 1, wherein processing the response includes transferring response data from the designated response processing page to the originating webpage.

9. A method for cross-domain communication between a sender domain and a receiver domain that is different from the sender domain, comprising:

sending a data request from an originating webpage deployed in the sender domain to the receiver domain, the data request being directed to a designated request processing page in the receiver domain, wherein sending the data request from the sender domain to the receiver domain includes opening a hidden page and using the hidden page to open the designated response processing page and to send a request command and associated request data via the hidden page, wherein opening the hidden page includes opening an invisible new window or an invisible iframe;

receiving a response from the receiver domain, the response including requested data and being directed to a designated response processing page in the sender domain, wherein the designated response processing page deployed in the sender domain is a different webpage from the originating webpage deployed in the sender domain; and

processing, by one or more hardware processors, the response.

10. The method of claim 9, wherein the data request is sent in response to a client action from a browser to an originating webpage in the sender domain.

11. The method of claim 9, wherein the designated request processing page is deployed in the receiver domain and the designated response processing page is deployed in the sender domain prior to the cross-domain communication.

12. The method of claim 9, wherein the data request includes a request command and associated request data that are sent via a Hypertext Transfer Protocol (HTTP) GET command.

13. The method of claim 9, wherein:

the data request includes a request command and associated request data;

the request command is sent as a fragment identifier attached to a uniform resource locator (URL); and

the associated data are transferred as a name property of a window object.

14. The method of claim 9, wherein:

the data request includes a request command and associated request data;

the request command and the associated request data are sent as a fragment identifier attached to a URL.

15. The method of claim 9, wherein request is transferred as a string in JSON format.

16. A receiver system for cross-domain communication between a sender domain and a receiver domain that is different from the sender domain, comprising:

a processor configured to;

receive, in the receiver domain, a data request from an originating webpage deployed in the sender domain, the data request being directed to a designated request processing page in the receiver domain, wherein sending the data request from the sender domain to the receiver domain includes opening a hidden page and using the hidden page to open the designated response processing page and to send a request command and associated request data via the hidden page, wherein opening the hidden page includes opening an invisible new window or an invisible iframe;

process the data request to generate a response; and

send the response to the sender domain, the response being directed to a designated response processing page in the sender domain, wherein the designated response processing page deployed in the sender domain is a different webpage from the originating webpage deployed in the sender domain; and

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

17. A method for cross-domain communication between a sender domain and a receiver domain that is different from the sender domain, comprising:

receiving, in the receiver domain, a data request from an originating webpage deployed in the sender domain, the data request being directed to a designated request processing page in the receiver domain, wherein sending the data request from the sender domain to the receiver domain includes opening a hidden page and using the hidden page to open the designated response processing page and to send a request command and associated request data via the hidden page, wherein opening the hidden page includes opening an invisible new window or an invisible iframe;

processing, by one or more hardware processors, the data request to generate a response; and

sending the response to the sender domain, the response being directed to a designated response processing page in the sender domain, wherein the designated response processing page deployed in the sender domain is a different webpage from the originating webpage deployed in the sender domain.