Distributing and synchronizing objects

• US 8,255,895 B2
• Filed: 03/31/2011
• Issued: 08/28/2012
• Est. Priority Date: 05/10/1999
• Status: Expired due to Fees

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Gates, Patrick, Federighi, Craig, Noyau, Eric
• Primary Examiner(s): Deng, Anna
• Application Number:
  US13/077,885
• Publication Number:
  US 20110179192A1
• Time in Patent Office: 516 Days
• Field of Search: 717168-172
• US Class Current: 717/168
• CPC Class Codes: G06F 16/178 Techniques for file synchronisation in file systems
• CPC Class Codes: G06F 16/182 Distributed file systems
• 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 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: G06F 8/656 while running
• CPC Class Codes: G06F 8/658 Incremental updates; Differential updates
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 61/4553 Object oriented directories, e.g. common object request broker architecture [CORBA] name server
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method and apparatus for distributing and synchronizing objects. One or more embodiments of the invention provide for distributing copies of the objects locally. By copying objects (including the data and behavior for the object) into local address space, the object'"'"'s methods may be executed locally thereby avoiding excessive network traffic. The state of the various object copies across a network may not be synchronized due to local changes and modifications. To synchronize the objects, one or more embodiments of the invention provide for the use of a policy that specifies conditions as to when objects are synchronized. Embodiments of the invention provide flexibility in setting the policy to accommodate varying applications. For example, a policy may provide for synchronization that is based temporally (e.g., every 10 minutes or daily at 10:00 P.M.). Alternatively, a policy may provide for synchronization based on the type or number of messages transmitted. In one or more embodiments, a default policy may be utilized that provides for the synchronization of local objects whenever a client issues a request from the remote server. In such an embodiment, the remote server transmits any updated object information when it responds to the local object request. The updated object information may be utilized to synchronize the objects.

Claims

1. A method for synchronizing distributed software objects comprising:

sending to a client from a server, in response to a request received via a network from the client to the server, a first object comprising one or more methods and one or more data values;

sending to the client a synchronization policy that requires the one or more data values of the first object to be sent to the server for synchronization upon occurrence at the client of a prescribed interaction;

receiving from the client a network communication comprising a data value of the first object; and

sending to the client from the server, in response to the network communication, a response data that includes an update to a data value of a second object sent previously by the server to the client, wherein the response data is determined at the server at least in part by using the data value of the second object associated with the first object to perform an action, and the response data updates the one or more data values of the first object based on the synchronization policy.

2. The method of claim 1, wherein the server is configured to propagate the data value of the first object to one or more other clients to which other copies of the first object have been sent.

3. The method of claim 1, wherein the data value of the first object is used at the server to update a data value of a remote object at the server of which the remote object at the client is a local copy.

4. The method of claim 1 the data value of the first object is used at the server to update a data value of a remote object at the server with which the remote object at the client is associated but of which the object at the client is not an exact duplicate copy.

5. A server system comprising:

a network communication interface; and

a processor coupled to the network communication interface and configured to;

send to a client, in response to a request received via the network communication interface, a first object comprising one or more methods and one or more data values;

sending to the client a synchronization policy that requires the one or more data values of the first object to be sent to the server for synchronization upon occurrence at the client of a prescribed interaction;

receiving from the client via the network communication interface a network communication comprising a data value of the first object; and

sending to the client, in response to the network communication, a response data that includes an update to a data value of a second object sent previously by the server to the client, wherein the response data is determined at the server at least in part by using the data value of the second object associated with the first object to perform an action, and the response data updates the one or more data values of the first object based on the synchronization policy.

6. The system of claim 5, wherein the response data includes updates to one or more data values of another object at the client.

7. The system of claim 5, wherein the server is configured to propagate the data value of the first object to one or more other clients to which other copies of the first object have been sent.

8. The system of claim 5, wherein the data value of the first object is used at the server to update a data value of a remote object at the server of which the object at the client is a local copy.

9. The system of claim 5, the corresponding data value at the server comprises a data value of a remote object at the server with which the remote object at the client is associated but of which the object at the client is not an exact duplicate copy.

10. A computer program product comprising:

a non-transitory computer usable medium having computer readable program code embodied therein which when executed by a computer causes the computer to synchronize distributed software objects, said computer program product comprising computer readable code which when executed by a computer causes the computer to perform the steps of;

sending to a client from a server, in response to a request received via a network from the client to the server, a first object comprising one or more methods and one or more data values;

sending to the client a synchronization policy that requires the one or more data values of the first object to be sent to the server for synchronization upon occurrence at the client of a prescribed interaction;

receiving from the client a network communication comprising a data value of the first object; and

sending to the client from the server, in response to the network communication, a response data that includes an update to a data value of a second object sent previously by the server to the client, wherein the response data is determined at the server at least in part by using the data value of the second object associated with the first object to perform an action, and the response data updates the one or more data values of the first object based on the synchronization policy.

11. The computer program product of claim 10, further comprising computer readable code which when executed by the computer causes the computer to perform the step of propagating the data value of the first object to one or more other clients to which other copies of the first object have been sent.