Data sharing system and method

• US 20070129958A1
• Filed: 12/01/2006
• Published: 06/07/2007
• Est. Priority Date: 12/07/2005
• Status: Abandoned Application

• Current Assignee: Calyx Technology, Inc.
• Original Assignee: Calyx Technology, Inc.
• Inventors: Wu, Benjamin, Park, Seongho
• Application Number:
  US11/607,536
• Publication Number:
  US 20070129958A1
• Time in Patent Office: Days
• US Class Current: 705/38
• CPC Class Codes: G06F 9/544 Buffers; Shared memory; Pipes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03
• CPC Class Codes: G06Q 40/03 Credit; Loans; Processing thereof

Abstract

System and method for sharing data between a 3^rd party website and a desktop application program on a user'"'"'s computer, wherein the web pages of the 3^rd party website access data associated with the application program such that the 3^rd party web pages drive the data exchange. The 3^rd party website is opened within a browser embedded within the desktop application program resident in a memory space on a user'"'"'s computer and the web pages of the 3^rd party website are allowed access to the data associated with the desktop application. Restrictions may be placed on the access given to the 3^rd party web pages so that only data and information that is needed is accessed. The data associated with the desktop application may be stored in the memory space of the desktop application program, stored on the user'"'"'s computer, or stored in a data source operably connected to the desktop application program.

Claims

1. A data sharing method comprising the steps of:

opening a 3^rd party website in a browser embedded within a desktop application resident in a memory space on a user'"'"'s computer; and

allowing web pages of the 3^rd party website to access data associated with the desktop application.

2. The method of claim 1, wherein the web pages of the 3^rd party website read and write the data associated with the desktop application.

3. The method of claim 2, wherein the web pages of the 3^rd party website drive the data sharing, such that the web pages of the 3^rd party website control both the reading and writing of data associated with the desktop application.

4. The method of claim 1, wherein the user selects and opens the 3^rd party website from a list of entries displayed in the desktop application.

5. The method of claim 4, wherein each list entry includes a profile associated with a particular 3^rd party website, and wherein the profile:

(a) limits the web pages of the particular 3^rd party website displayable in the desktop application; and

/or (b) limits the data associated with the desktop application accessible to the particular 3^rd party website.

6. The method of claim 5, wherein information included in the profiles is updatable by a vendor of the desktop application.

7. The method of claim 1, wherein a user decides which data is accessible to the 3rd party website.

8. The method of claim 1, wherein the web pages of the 3^rd party website select the data associated with the desktop application for reading and writing.

9. The method of claim 1, wherein the web pages of the 3^rd party website select a format of the data associated with the desktop application for reading and writing.

10. The method of claim 1, wherein the web pages of the 3^rd party website write its own unique identifier to the data associated with the desktop application.

11. The method of claim 10, wherein the unique identifier is read by the web pages of the 3^rd party website during subsequent data accesses.

12. The method of claim 10, wherein the unique identifier is used by a vendor of the desktop application for billing purposes.

13. The method of claim 1, wherein the desktop application allows the 3^rd party web pages to access the data associated with the desktop application in real time.

14. The method of claim 1, wherein the data associated with the desktop application accessible by the 3^rd party web pages includes only a data block resident in the memory space of the desktop application.

15. The method of claim 14, wherein the data block comprises a data file opened in the memory space of the desktop application.

16. The method of claim 1 wherein the data associated with the desktop application is stored in a data source operably connected to the desktop application.

17. The method of claim 1, further comprising the step of allowing the 3^rd party website to store a 3^rd party specific document in the data associated with the desktop application.

18. The method of claim 1, allowing the 3^rd party website to store a status indicator in the data associated with the desktop application, wherein the status indicator provides a status of services performed by the 3^rd party.

19. The method of claim 1, wherein the desktop application is a loan origination software program.

20. The method of claim 1, wherein the data comprises mortgage loan data.

21. A data sharing system comprising:

a desktop application resident in a memory space on a user'"'"'s computer; and

a web browser embedded within the desktop application;

wherein the desktop application includes a data proxy coupling data associated with the desktop application with the web pages of a 3^rd party website opened within the web browser, and

wherein data associated with the desktop application is accessible by the 3^rd party web pages via the data proxy.

22. The data sharing system of claim 21, wherein the web pages of the 3^rd party website read and write the data associated with the desktop application.

23. The data sharing system of claim 22, wherein the web pages of the 3^rd party website drive the data sharing, such that the web pages of the 3^rd party website control both the reading and writing of data associated with the desktop application.

24. The data sharing system of claim 21, wherein the user selects and opens the 3^rd party website from a list of entries displayed in the desktop application.

25. The data sharing system of claim 21, wherein the desktop application further includes a data limiter provided between the 3^rd party web pages and the data proxy, wherein the data limiter controls access of the data associated with the desktop application by the 3^rd party web pages.

26. The data sharing system of claim 25, wherein the desktop application includes profiles associated one each with particular 3rd party websites, wherein each profile:

(a) limits the web pages of the particular 3^rd party website displayable in the desktop application; and

/or (b) limits, via the data limiter, the data associated with the desktop application accessible to the particular 3^rd party website.

27. The data sharing system of claim 26, wherein information included in the profiles is updatable by a vendor of the desktop application.

28. The data sharing system of claim 21, wherein a user decides which data is accessible to the 3rd party website.

29. The data sharing system of claim 21, wherein the web pages of the 3^rd party website select the data associated with the desktop application for reading and writing.

30. The data sharing system of claim 21, wherein the web pages of the 3^rd party website select a format of the data associated with the desktop application for reading and writing.

31. The data sharing system of claim 21, wherein the web pages of the 3^rd party website write its own unique identifier to the data associated with the desktop application.

32. The data sharing system of claim 31, wherein the unique identifier is read by the web pages of the 3^rd party website during subsequent data accesses.

33. The data sharing system of claim 31, wherein the unique identifier is used by a vendor of the desktop application for billing purposes.

34. The data sharing system of claim 21, wherein the desktop application allows the 3^rd party web pages to access the data associated with the desktop application in real time.

35. The data sharing system of claim 21, wherein the data associated with the desktop application accessible by the 3^rd party web pages includes only a data block resident in the memory space of the desktop application.

36. The data sharing system of claim 35, wherein the data block comprises a data file opened in the memory space of the desktop application.

37. The data sharing system of claim 35, wherein the desktop application further includes a data limiter provided between the 3^rd party web pages and the data proxy, wherein the data limiter limits access of the 3^rd party web pages to only data stored in the data block.

38. The data sharing system of claim 35, wherein the desktop application includes a deserializer retrieving the data block from a data source operably connected to the desktop application and storing the data block in the memory space of the desktop application.

39. The data sharing system of claim 35, wherein the desktop application includes a serializer retrieving the data block from the memory space of the desktop application and storing the data block in a data source operably connected to the desktop application.

40. The data sharing system of claim 21, wherein the data associated with the desktop application is stored in a data source operably connected to the desktop application.

41. The data sharing system of claim 21, wherein the 3^rd party web pages include a client-side script interfacing with the data proxy, wherein the data proxy responds to a request for data made by the client-side script.

42. The data sharing system of claim 21, wherein the web pages of the 3^rd party website store a 3^rd party specific document in the data associated with the desktop application.

43. The data sharing system of claim 21, wherein the web pages of the 3^rd party website store a status indicator in the data associated with the desktop application, wherein the status indicator provides a status of services performed by the 3^rd party.

44. The data sharing system of claim 21, wherein the desktop application is a loan origination software program.

45. The data sharing system of claim 21, wherein the data comprises mortgage loan data.