Declarative synchronization of shared data

• US 9,898,517 B2
• Filed: 04/21/2006
• Issued: 02/20/2018
• Est. Priority Date: 04/21/2006
• Status: Active Grant

• Current Assignee: Adobe Inc.
• Original Assignee: Adobe Systems Incorporated (Adobe Inc.)
• Inventors: Staczek, Jason
• Primary Examiner(s): Thomas, Ashish K
• Assistant Examiner(s): Mahmood, Rezwanul
• Application Number:
  US11/408,644
• Publication Number:
  US 20130166507A1
• Time in Patent Office: 4,323 Days
• Field of Search: 707 10, 707201, 707203, 707610, 707640, 707661
• CPC Class Codes: G06F 16/27 Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes

Abstract

Methods and apparatus, including computer systems and program products, related to declarative synchronization of shared data. One method includes receiving one or more changes to data maintained by one of multiple computer programs having respective local copies of the data, identifying an event characterizing synchronization of the data maintained by the computer program with the other computer programs (e.g., with a local copy managed by the other computer program), and initiating synchronization of the changes with one of the other programs having respective local copies (e.g., with the local copy managed by the other program) in response to the event occurring. The event can be characterized by an annotation. Identifying an event can include reading a property of a data object (e.g., in a data object graph of shared data).

Claims

1. A method comprising:

receiving one or more changes, by one or more computing devices, to a copy of data maintained by a computer program being one of a plurality of computer programs having respective local copies of the data;

marking an object graph, by the one or more computing devices, as a first buffering of the changes at the computer program to indicate which of one or more data objects correspond to the changes such that the changes are unavailable for being committed to the plurality of computer programs, wherein individual data objects represent a runtime version of specific data and implement specified synchronization behavior for the runtime version of the specific data that the individual data object represents, the synchronization behavior being implemented by compiled code, included in the data object, that represents the synchronization behavior that is to occur on the occurrence of an event, the event including a change of focus of a user interface element;

initiating synchronization of the changes after marking the object graph, by the one or more computing devices, with one or more of the plurality of computer programs having the respective local copies in response to the event occurring, the initiating synchronization of the changes comprising a second buffering of the changes at the computer program such that the changes are available for being committed to the plurality of computer programs, the event causing synchronization of the one or more changes to be postponed until an associated node defined as a master is changed.

2. The method of claim 1, wherein the compiled code comprises byte code executable in a runtime system in conformance with a JAVA standard for runtime systems.

3. The method of claim 1, wherein specified synchronization behaviors are specified by an associated annotation written in accordance with a tree-structured format.

4. The method of claim 3, wherein the tree-structured format specifies that annotations are written for a granularity of one or more nodes of a tree and annotations of a node apply to nodes in the tree nested within the node.

5. The method of claim 1, wherein the initiating synchronization of the changes comprises buffering the changes in an outgoing queue of changes at the one or more computing devices where the computer program resides.

6. The method of claim 1 wherein the plurality of computer programs comprises one or more server systems and one or more client systems.

7. The method of claim 6, wherein the operations comprise committing the changes to the one or more server systems from the one or more client systems where the computer program resides.

8. The method of claim 7, wherein the committing the changes to the one or more server systems comprises committing the changes in response to a request from the one or more server systems to receive changes queued by the one or more client systems.

9. The method of claim 7, wherein the committing the changes to the one or more server systems comprises committing the changes as a result of a push of the changes to the one or more server systems from the one or more client systems.

10. The method of claim 6 wherein the initiating synchronization further comprises bypassing the one or more server systems and synchronizing the one or more changes between two or more of the one or more client systems.

11. The method of claim 1 wherein the specified synchronization behavior includes one set of client-side annotations and one set of server-side annotations.

12. A system comprising:

one or more computing devices configured to perform operations comprising;

receiving one or more changes to a copy of data maintained by a computer program being one of a plurality of computer programs having respective local copies of the data;

marking an object graph as a first buffering of the changes at the computer program to indicate which of one or more data objects correspond to the changes such that the changes are unavailable for being committed to the plurality of computer programs, wherein individual data objects represent a runtime version of specific data and implement specified synchronization behavior for the runtime version of the specific data that the individual data object represents, the synchronization behavior being implemented by compiled code, included in the data object, that represents the synchronization behavior that is to occur on the occurrence of an event, the event including a change of focus of a user interface element;

initiating synchronization of the changes after the marking of the object graph with one or more of the plurality of computer programs having the respective local copies in response to an event occurring as specified in a data object, the initiating synchronization of the changes comprising a second buffering of the changes at the computer program such that the changes are available for being committed to the plurality of computer programs, the event causing synchronization of the one or more changes to be postponed until an associated node defined as a master is changed.

13. The system of claim 12, wherein the specified synchronization behavior is specified by a compiled annotation that includes a reference to a set of data and a trigger attribute describing the event.

14. The system of claim 12, wherein the compiled code comprises byte code executable in a runtime system in conformance with a JAVA standard for runtime systems.

15. The system of claim 14, wherein specified synchronization behaviors are specified by an associated annotation written in accordance with a tree-structured format.

16. The system of claim 12, wherein the initiating synchronization of the changes comprises buffering the changes in an outgoing queue of changes at the one or more computing devices where the computer program resides.

17. The system of claim 12, wherein the plurality of computer programs comprises one or more server systems and one or more client systems.

18. The system of claim 17, wherein the operations comprise committing the changes to the one or more server systems from the one or more client systems where the computer program resides.

19. A machine-readable device, tangibly embodying a computer program product configured to cause a data processing apparatus to perform operations comprising:

receiving one or more changes to a copy of data maintained by a computer program being one of a plurality of computer programs having respective local copies of the data;

marking an object graph as a first buffering of the changes at the computer program to indicate which of one or more data objects correspond to the changes such that the changes are unavailable for being committed to the plurality of computer programs, wherein individual data objects represent a runtime version of specific data and implement specified synchronization behavior for the runtime version of the specific data that the individual data object represents, the synchronization behavior being implemented by compiled code, included in the data object, that represents the synchronization behavior that is to occur on the occurrence of an event, the event including a change of focus of a user interface element;

initiating synchronization of the changes after the marking of the object graph with one or more of the plurality of computer programs having the respective local copies in response to the event occurring, the initiating synchronization of the changes comprising a second buffering of the changes at the computer program such that the changes are available for being committed to the plurality of computer programs, the event causing synchronization of the one or more changes to be postponed until an associated node defined as a master is changed.

20. The machine-readable device of claim 19, wherein the specified synchronization behavior is specified by a compiled annotation that includes a reference to a set of data and a trigger attribute describing the event.