MANAGEMENT OF DATA OBJECT SHARING AMONG APPLICATIONS
Presented are a system and method for sharing data objects among applications. Included is a data protocol layer that permits a flow of data messages among the applications, where a portion of the data messages include data objects stored in a data store. A client library is coupled between the applications and the data protocol layer. A data request module associated with each client library requests data objects from the data stores that match a particular data-object set. A management server receives the request, parses the request, retrieves any matching data objects, and causes the return of the any matching data objects to the data request module. Associated with the management server is a registration module that accepts subscriptions from subscribing applications. An event notification module associated with the management server compares a data object in a data message with the subscriptions, and notifies the subscribing applications in response.
1 . A computer-implemented system configured to manage data object sharing among applications, comprising:
a computer having a processor, a memory, and being configured to execute a first application;
a set of code (SOC);
a client library associated with the first application and in communication with the SOC, the client library being operable to:
request from the SOC the data object type definition,
receive an event notification from the SOC comprising changes to the data object type definition by a second application that is different than the first application;
dynamically change an internal representation of the data type definition used by the first application in response to the event notification and the changes received from the SOC, and
manage a plurality of data objects defined in accordance with the changed data object type definition;
wherein the SOC either executes on the computer as part of the client library or executes on a machine in communication with the client library.
2 . The system of claim 1 , wherein the first application exchanges the portion of the data objects with at least the second application.
3 . The system of claim 2 , wherein the data object type definition is included within one or more of the data objects.
4 . The system of claim 1 , wherein the data object type definition is included within one or more of the data objects.
5 . The system of claim 1 , wherein there are plural applications each having an associated client library, and wherein each client library comprises the SOC and performs the functionality thereof.
6 . The system of claim 1 , wherein the data object type definition comprises at least one strongly typed definition.
7 . The system of claim 1 , wherein the data object type definition comprises at least one field linking to another data type.
8 . The system of claim 7 , wherein the data object type definition comprises at least one data type that inherits from a parent data type.
9 . The system of claim 1 , wherein the data object type definition comprises at least one data type that inherits from a parent data type.
10 . The system of claim 1 , wherein the data type definition comprises an indicator that a particular data object type is one of transient, persistent, or history-enabled.
11 . The system of claim 1 , wherein the data type definition comprises an indicator that a particular data field of one of the plurality of data objects is at least one of linked and coupled.
12 . The system of claim 1 , wherein the data object type definition is versioned.
13 . The system of claim 1 , wherein the data object type definition is serialized into a string or file format.
14 . The system of claim 1 , wherein a subset of the data objects comprise security and access control information concerning which data objects the client library can read and/or write.
15 . The system of claim 1 , wherein the client library is further configured to cast one or more data objects from one data type to another.
16 . The system of claim 1 , wherein one or more of the plurality of data objects has a field comprising a coupled second data object.
17 . The system of claim 1 , wherein one or more of the plurality of data objects has an object hook executable by the client library in response to a specified action.
18 . The system of claim 1 , wherein one or more of the plurality of data objects has a local property setter or getter.
19 . The system of claim 1 , wherein the client library is further configured to pass one or more of the plurality of data objects as a value or reference type.
20 . A computer-implemented method for managing data-object sharing among at least a first application and a second application, each application executing in a computer having a processor and a memory;
associating a client library with at least the first application;
executing a set of code (SOC) either as part of the client library or on a machine in communication with the client library,
requesting at the first application a data object type definition from the SOC;
receiving the data object type definition at the first application;
dynamically changing an internal representation of the data type definition used by the first application in response to an event notification from the SOC, the event notification identifying changes to the data object type definition made by the second application, and
managing a plurality of data objects defined in accordance with the changed data object type definition.