Method and system to provide message communication between different browser based applications running on a desktop

• US 7,519,689 B2
• Filed: 09/10/2003
• Issued: 04/14/2009
• Est. Priority Date: 09/10/2003
• Status: Active Grant

• Current Assignee: Alvaria Incorporated
• Original Assignee: Aspect Software Incorporated
• Inventors: Pandurangan, Krishnakumar, Mohan, Prabhuram
• Primary Examiner(s): Meky; Moustafa M
• Assistant Examiner(s): Chea; Philip J
• Application Number:
  US10/660,418
• Publication Number:
  US 20050055458A1
• Time in Patent Office: 2,043 Days
• Field of Search: 709/238, 709/203, 709/217, 709/219, 713/153
• US Class Current: 709/219
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and system to facilitate the communication of data and/or messages between different Internet domains include, at a first application associated with a first Internet domain, embedding data in an anchor portion of a URL string. The URL string identifies a second Internet domain that is different from the first Internet domain. This URL string is communicated to a second application associated with the second Internet domain. At the second application, the received URL string is parsed, and the relevant data extracted therefrom.

Claims

1. A method to communicate data between different Internet domains, the method including:

at a first application supported within a browser instance and associated with a first Internet domain, embedding the data in an anchor portion of a URL string that identifies a second Internet domain that is different from the first Internet domain where the first application is prohibited by browser same origin policy from communicating data with a second application supported within another browser instance and associated with the second Internet domain wherein the first application and the second application reside on a common machine;

embedding an identifier, that identifies the second application, within the URL string;

communicating the URL string to the second application associated with the second Internet domain; and

at the second application, receiving the URL string and extracting the data therefrom,

wherein the receiving of the URL string at the second application does not cause the second application to perform a server access to a server associated with the second domain and wherein the first application invokes execution of the second application by communicating the URL string to the server associated with the second domain.

2. The method of claim 1, wherein the second application communicates the data to a third application, associated with the second Internet domain, the third application communicating the data to an application server associated with the second Internet domain.

3. The method of claim 2, wherein the second application communicates the data to a client of the third application, wherein both the client of the third application and the second application reside on a common machine.

4. The method of claim 1, including communicating one or more additional URL strings to the second application, each additional URL string including further data embedded in a respective anchor portion of each additional URL string.

5. The method of claim 1, including, at the second application, periodically determining whether a new URL string has been received and, if so, extracting further data from an anchor portion of the new URL string.

6. The method of claim 5, wherein the second application includes client-side executable logic to determine receipt of the new URL string.

7. The method of claim 1, including, at the first application, embedding an identifier for the second application within the URL string, thereby to cause download of the second application from the second Internet domain.

8. A system to communicate data between different Internet domains, the system comprising:

a first application associated with a processor supported within a browser instance, and associated with a first Internet domain, to embed the data in an anchor portion of a URL string that identifies a second Internet domain that is different from the first Internet domain, to embed an identifier that identifies a second application within the URL string where the first application is prohibited by browser same origin policy from communicating data with the second application supported within another browser instance and associated with the second Internet domain, the first and second application residing on a common machine and to

communicate the URL string to the second application associated with the second Internet domain; and

the second application to receive the URL string and to extract the data therefrom,

wherein the second application does not perform a server access to a server associated with the second domain responsive to receipt of the URL string and wherein the first application invokes execution of the second application by communicating the URL string to the server associated with the second domain.

9. The system of claim 8, including a third application associated with the second Internet domain, wherein the second application is to communicate the data to a third application, and the third application is to communicate the data to an application server associated with the second Internet domain.

10. The system of claim 9, wherein the second application is to communicate the data to a client of the third application, wherein both the client of the third application and the second application reside on a common machine.

11. The system of claim 8, wherein the first application is to communicate one or more additional URL strings to the second application, each additional URL string including further data embedded in a respective anchor portion of each additional URL string.

12. The system of claim 8, wherein the second application is periodically to determine whether a new URL string has been received and, if so, to extract further data from an anchor portion of the new URL string.

13. The system of claim 12, wherein the second application includes client-side executable logic to determine receipt of the new URL string.

14. The system of claim 8, wherein the first application is to embed an identifier for the second application within the URL string, thereby to cause download of the second application from the second Internet domain.

15. A system to communicate data between different Internet domains the system including:

first means associated with a processor, associated with a first Internet domain, for embedding the data in an anchor portion of a URL string from the first domain, the anchor portion of the URL string identifying a second Internet domain that is different from the first Internet domain for embedding an identifier, that identifies second means, within the URL string, and for communicating the URL string to second means associated with the second Internet domain wherein the first means and the second means function on a common machine, and;

the second means for receiving the URL string and for extracting the data therefrom,

wherein the second means does not perform a server access to a server associated with the second domain responsive to receipt of the URL string and wherein the first means invokes execution of the second means by communicating the URL string to the server associated with the second domain.

16. A machine-readable medium storing a set of instructions, executable by a machine, to cause the machine to communicate data between different Internet domains utilizing a method, including:

at a first application associated with a first Internet domain, embedding the data in an anchor portion of a URL string that identifies a second Internet domain that is different from the first Internet domain wherein the first application and a second application reside on a common machine;

embedding an identifier, that identifies the second application, within the URL string;

communicating the URL string to the second application associated with the second Internet domain; and

at the second application, receiving the URL string and extracting the data therefrom,

wherein the receiving of the URL string at the second application does not cause the second application to perform a server access to a server associated with the second domain and wherein the first application invokes execution of the second application by communicating the URL string to the server associated with the second domain.