Method and system to provide message communication between different application clients running on a desktop

• US 20060075069A1
• Filed: 09/24/2004
• Published: 04/06/2006
• Est. Priority Date: 09/24/2004
• Status: Abandoned Application

• Current Assignee: Aspect Communications Corporation (Alvaria Incorporated)
• Original Assignee: Aspect Communications Corporation (Alvaria Incorporated)
• Inventors: Mohan, Prabhuram, Pandurangan, Krishnakumar, Venkatesh, Chathnaur
• Application Number:
  US10/950,239
• Publication Number:
  US 20060075069A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

A method and system to facilitate the communication of data and/or messages between a browser-based application and a non browser-based application including, at the browser-based application, embedding data in an anchor portion of a URL string and invoking execution of an embedded browser component of the non browser-based application by communicating the URL string to the second application. At the non browser-based application, the received URL string is parsed and the relevant data extracted therefrom.

Claims

1. A method to communicate data between a first application client and a second application client, the method including:

at the first application client, embedding data in an anchor portion of a URL string that identifies a message content;

at the first application client, invoking execution of an embedded browser component of the second application client by communicating the URL string to the second application client; and

at the second application client, parsing the URL string and extracting the data therefrom,

wherein the parsing of the URL string at the second application client causes the second application client to perform a function using the data.

2. The method of claim 1, wherein the first application client is browser-based and the second application client is non-browser based.

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

4. The method of claim 1, further including, embedding the browser component in the second application.

5. The method of claim 4, wherein the embedding of the browser component includes providing a browser window control.

6. The method of claim 1, wherein the performing of the function using the data includes accessing a server associated with the URL string.

7. The method of claim 6, further including, at the second application client, receiving a result of the function from the server.

8. The method of claim 7, further including, at the second application client, displaying the result of the function.

9. The method of claim 7, further including, at the second application client, returning the result of the function to the first application client.

10. The method of claim 9, further including, at the first application client, displaying the result of the function in a browser window.

11. The method of claim 1, wherein the performing of the function using the data includes providing a third application client with the data.

12. The method of claim 11, wherein the third application client is non-browser based.

13. The method of claim 12, wherein the second application client includes a sending control and third application client includes a receiving control, the sending control and the receiving control determining a communication protocol between the second application client and the third application client.

14. The method of claim 13, wherein the first application client, the second application client and the third application client reside on a common machine.

15. The method of claim 11, further including, at the third application client, performing a further function using the data.

16. The method of claim 15, wherein the performing of the further function using the data includes accessing a server associated with the URL string.

17. The method of claim 16, further including, at the third application client, receiving a result of the further function from the server and providing the result of the function to the second application client.

18. The method of claim 17, further including, at the second application client, displaying the result of the function.

19. The method of claim 16, further including, at the third application client, receiving a result of the function from the server and displaying the result of the function.

20. A system to communicate data between a first application client and a second application client, the system including:

the first application client to embed data in an anchor portion of a URL string that identifies a message content and to communicate the URL string to a second application client to invoke execution of an embedded browser component of a second application client; and

the second application client to parse the URL string, extract the data therefrom and to perform a function using the data.

21. The system of claim 20, wherein the first application client is browser-based and the second application client is non-browser based.

22. The system of claim 21, wherein both the first application client and the second application client reside on a common machine.

23. The system of claim 20, wherein the second application client is to perform the function using the data by accessing a server associated with the URL string.

24. The system of claim 23, wherein the second application client is to receive a result of the function from the server.

25. The system of claim 24, wherein the second application client is to display the result of the function.

26. The system of claim 24, wherein the second application client is to return the result of the function to the first application client.

27. The system of claim 26, wherein the first application client is to display the result of the function in a browser window.

28. The system of claim 20, wherein the second application client is toperform the function using the data by providing a third application client with the data.

29. The system of claim 28, wherein the third application client is non-browser based.

30. The system of claim 29, wherein the second application client includes a sending control and third application client includes a receiving control, the sending control and the receiving control determining a communication protocol between the second application client and the third application client.

31. The system of claim 30, wherein the first application client, the second application client and the third application client reside on a common machine.

32. The system of claim 28, wherein the third application client is to perform a further function using the data.

33. The system of claim 32, wherein the third application client is to perform the further function using the data by accessing a server associated with the URL string.

34. The system of claim 33, wherein the third application client is to receive a result of the further function from the server and to provide the result of the function to the second application client.

35. The system of claim 34, wherein the second application client is to display the result of the function.

36. The system of claim 33, wherein the third application plant is to receive a result of the function from the server and to display the result of the function.

37. A machine-readable medium storing a set of instructions that, when executed by machine, cause the machine to facilitate communication of data between a browser-based application and a first non browser-based application utilizing a method, the method including:

at the browser-based application, embedding a data in an anchor portion of a URL strings that identifies a message content;

at the browser-based application, invoking execution of an embedded browser component of the first non browser-based application by communicating the URL string to the first non browser-based application; and

at the first non browser-based application, parsing the URL string and extracting the data therefrom,

wherein the parsing of the URL string at the first non browser-based application causes the first non browser-based application to perform a function using the data.

38. The machine-readable medium of claim 37, wherein the browser-based application and the first non browser-based application reside on a common machine.

39. A system to communicate data between a first application client and a second application client, the system including:

first means for embedding data in an anchor portion of a URL string that identifies a message content and for communicating the URL string to a second application client to invoke execution of an embedded browser component of a second application client; and

second means for parsing the URL string, extracting the data therefrom and performing a function using the data.