SYSTEM FOR SHARING DATA OBJECTS AMONG APPLICATIONS

• US 20090254601A1
• Filed: 06/08/2009
• Published: 10/08/2009
• Est. Priority Date: 09/02/2004
• Status: Active Grant

• Current Assignee: Bloomberg Finance Holdings L P, Bloomberg Finance LP (Bloomberg LP)
• Original Assignee: Broadway Technology LLC (ION Investment Group Ltd.)
• Inventors: Walsky, Joshua, Moeller, Tyler
• Granted Patent: US 7,970,823 B2
• Time in Patent Office: Days
• US Class Current: 709/201
• CPC Class Codes: G06F 12/0806 Multiuser, multiprocessor or multiprocessing cache systems
• CPC Class Codes: G06F 2209/544 Remote
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

System and method for sharing data objects among applications. A portion of the data messages includes data objects. A client library is coupled to a requesting application. A client library requests data objects of a data-object set. Requests from the client library are received and parsed by a set of code (SOC) that performs tasks so as to retrieve any matching data objects and cause the return of such matching data objects to the client library. A registration module registers subscriptions from or on behalf of the applications and an event notification module compares a data object in an event message with the subscriptions and notifies the subscribed applications in response. The system can respond to requests in either a query or a procedure call format.

Claims

1. A system for sharing data objects among applications, comprising:

a client library coupled to a requesting application and operable to request data objects of a data-object set;

a set of code (SOC) in communication with the client library and configured to parse any request from the client library and retrieve any data objects of the data-object set;

a registration module configured to register subscriptions from or on behalf of the requesting application, wherein each subscription has a filter criteria; and

an event notification module configured to receive an event message from the applications, compare the at least one data object in the event message with one or more of the subscriptions, and selectively notify the subscribed applications, including at least the requesting application, in response to the comparison on the basis of any matches of the filter criteria,

wherein the selective notification includes a return of any matching data objects to the client library coupled to at least the requesting application; and

wherein the event notification module is operable to identify at least whether the event message indication is an out-of-scope or an into-scope event.

2. The system of claim 1, wherein the event notification module is further operable to return data objects that are out-of-scope.

3. The system of claim 1, wherein the subscription comprises a data-object set description described in a data-set definition language.

4. The system of claim 1, wherein the client library includes the SOC.

5. The system of claim 1, further comprising a data-type definition language that defines one or more data-types shareable among the applications through each of the respective client libraries, and wherein a data-set definition language defines data-object sets of a given data type.

6. The system of claim 1, wherein the SOC is configured to return any matching data to the client library.

7. The system of claim 1, wherein the SOC is configured to provide routing information needed to effectuate the return of any matching data to the client library.

8. The system of claim 1, wherein the data message flow is in one of a request/response mode and a publish/subscribe mode.

9. The system of claim 1, wherein the requesting application is written in a native language, and wherein the client library is configured to complement each respective application'"'"'s native language.

10. The system of claim 1, further comprising one or more data stores containing the data-object sets, wherein the data stores comprise at least one of a disc storage device, magnetic media storage device, holographic storage device, and a solid state memory device.

11. The system of claim 1, further comprising:

an object pool associated with at least one client library and containing instantiations of at least one of the data objects; and

a handle comprising a reference to one of the data objects in the object pool, wherein the client library is operable to return the handle to its coupled application so that any matching data objects and the selective notification are accessible to the requesting application.

12. The system of claim 11, wherein any matching data objects in the selective notification include revision information.

13. The system of claim 1, wherein the data objects are stored in a relational database.

14. The system of claim 1, further comprising a monitoring module in communication with each respective application and configured to monitor the status of the applications.

15. The system of claim 1, further comprising a statistical analysis module in communication with each respective application and configured to gather operational statistics of the applications.

16. The system of the claim 1, wherein the request defines the data-object set in a query format.

17. The system of claim 1, wherein the request comprises a procedural call.

18. The system of claim 1, wherein the request is one of:

the data-object set in a query format; and

a procedural call.

19. The system of claim 1, wherein the selective notifications are sent in one of a point-to-point mode and a broadcast mode.

20. The system of claim 1, further comprising a data-set definition language having one of a textual-based language readable by a human and a derivation of a standard query language having the addition of constructs that execute remote procedure calls.

21. The system of claim 1, further comprising:

a data cache that contains data objects that meet a data definition statement, wherein the data cache includes a handle to the data objects within the data cache.

22. The system of claim 21, wherein data objects are added and removed from the data cache at least in response to respective into-scope events and out-of-scope events.

35. The system of claim 1, wherein the comparing step comprises comparing the at least one data object with a filter associated with one or more of the subscriptions, and wherein the event notification module is further operable to identify whether the event message indicates an in-scope event.

23. A method for sharing data objects among applications, comprising:

providing a client library coupled to a requesting application;

permitting a flow of data messages among the applications, at least a portion of the data messages including at least one data object;

requesting, by the client library, data objects of a data-object set;

parsing the request from the client library and retrieving any data objects of the data-object set using a set of code (SOC);

registering, at a registration module, subscriptions from or on behalf of the requesting application, wherein the subscriptions have a filter criteria;

capturing, at an event notification module, an event message from one of the applications;

comparing at least one data object in the event message with one or more of the subscriptions using a filter; and

selectively notifying the subscribed applications, including the requesting application, in response to the comparison on the basis of any matches of the filter criteria,

wherein the selective notification causes a return of any matching data objects to the client library coupled to at least the requesting application, and

wherein the event notification module identifies at least whether the event message indicates an out-of-scope or an into-scope event.

24. The method of claim 23, including the additional step of returning, using the event notification module, data objects that are out-of-scope.

25. The method of claim 23, including the additional step of describing the subscription with a data-object set description described in a data-set definition language.

26. The method of claim 23, including the additional step of returning any matching data to the client library.

27. The method of claim 23, including the additional step of providing routing information effectuating the return of any matching data to the client library.

28. The method of claim 23, including the additional step of monitoring the status of the applications by a monitoring module in communication with each respective application.

29. The method of claim 23, including the additional step of gathering operational statistics of the applications by a statistical analysis module in communication with each respective application.

30. The method of claim 23, wherein the requesting step requests the data-object set in a query format.

31. The method of claim 23, wherein the requesting step includes the steps of:

defining the data-object set as a remote procedure call; and

returning a set of data from the remote procedure call.

32. The method of claim 23, wherein the requesting step comprises one of:

requesting data objects of the data-object set in a query format; and

requesting data objects of the data-object set using a procedural call.

33. The method of claim 23, including the additional steps of:

associating an object pool with the client library;

populating the object pool with an instantiation of at least one of the data objects; and

referencing one of the data objects in the object pool with a handle, wherein the client library returns the handle to its coupled application so that any matching data objects and the selective notification are accessible to the application.

34. The method of claim 33, wherein the selective notification contains data objects, wherein any matching data objects and the selective notification data objects include revision information.

36. A system for sharing data objects among applications, comprising:

a data protocol layer that permits a flow of data messages among applications, at least a portion of the data messages including at least one data object;

a client library coupled between a requesting application and the data protocol layer and operable to request data objects of a data-object set;

a set of code (SOC) in communication with the client library and configured to parse any request from the client library and retrieve any data objects of the data-object set;

a registration module configured to register subscriptions from or on behalf of the requesting application, wherein each subscription has a filter criteria; and

an event notification module configured to receive an event message from the applications, compare the at least one data object in the event message with one or more of the subscriptions, and selectively notify the subscribed applications, including at least the requesting application, in response to the comparison on the basis of any matches of the filter criteria,

wherein the selective notification includes a return of any matching data objects to the client library coupled to at least the requesting application; and

wherein the event notification module is operable to identify at least whether the event message indication is an out-of-scope or an into-scope event.