Synchronization and replication of object databases

• US 5,684,984 A
• Filed: 09/29/1994
• Issued: 11/04/1997
• Est. Priority Date: 09/29/1994
• Status: Expired due to Term

• Current Assignee: Apple Inc.
• Original Assignee: Apple Computer Incorporated (Apple Inc.)
• Inventors: Jones, Anne, Zarmer, Craig
• Primary Examiner(s): Black, Thomas G.
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US08/314,951
• Time in Patent Office: 1,132 Days
• Field of Search: 395/650, 395/157, 395/600, 395/425, 395/610, 395/611, 395/613, 395/614, 395/616, 395/479, 395/342, 364/408, 364/401, 348/7, 379/207
• US Class Current: 707/613
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: Y10S 707/966 Distributed
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface

Abstract

The present invention, generally speaking, provides a method of synchronizing information between a plurality of sites and a central location that solves number of potentially "thorny" problems of distributed database systems in an elegant and efficient manner. The first issue involves sychronizing different copies of an item on machines that are not continuously linked at which each copy may be changed independently. Rather than attempting to formulate a set of synchronization policies generally applicable to all items in all instances, synchronization policies are moved from the database engine to the items themselves. The second issue involves lifetime--knowing, given a complex set of interrelationship of items, when an item may be safely deleted. This problem is addressed by providing an interested party mechanism whereby items may "express interest" in each other. When no item is interested in a particular item, that item may safely "go away".

Claims

1. In a distributed database system, a method of synchronizing information between a plurality of sites and a central location, comprising the steps of, for each of said plurality of sites:

establishing a first database portion at the central location and a second data base portion at the site, where the second database portion is a substantial replica of the first database portion, wherein each of the first and second database portions comprise a plurality of named information items including information items to be output in such a way as to be perceived by a user, and wherein said plurality of named information items are managed at the central location by a database engine;

changing the second database portion at the site;

reporting changes in the second database portion to the central location;

at the central location, sending one or more messages describing changes in the second database portion to one or more named information items of the first database portion affected by the changes, without the database engine itself effecting the changes; and

the one or more named information items of the first database portion affected by the changes responding to the one or more messages describing changes in the second database portion by updating themselves to reflect the changes to the second database portion reported to the central location.

2. The method of claim 1, wherein the first database portion and the second database portion each comprise a plurality of information items.

3. The method of claim 2, wherein, at each of the plurality of sites and at the central location, multiple program entities, including information items, are allowed to subscribe to changes to any information item, comprising the further steps of, at each of the plurality of sites and at the central location:

registering a plurality of program entities as subscribing to changes to a particular information item;

changing the particular information item; and

broadcasting to each program entity registered as subscribing to changes to the information item a notice describing changes to the information item.

4. The method of claim 3, comprising the further steps of:

sending a synchronization notice from one of the sites to the central location a notice describing changes to an information item changed at the one site.

5. The method of claim 4, wherein each program entity and each information item is identified by a identifier, comprising the further steps of:

at the central location, sending the synchronization notice to a program entity having a same identifier as the information item changed at the one site, wherein the program entity is a corresponding information item corresponding to the information item changed; and

changing the corresponding information item to reflect changes to the information item changed at the one site.

6. The method of claim 5, comprising the further step of:

at the central location, broadcasting, to each program entity registered as subscribing to changes to the corresponding information item, a notice describing changes to the information item.

7. The method of claim 6, wherein each program entity includes a first program segment governing how that program entity will respond to notices, other than said synchronization notice, of changes to an information item to which the program entity has subscribed, comprising the further steps of:

receiving at each program entity registered as subscribing to changes to the information item the notice describing changes to the information item; and

at each program entity registered as subscribing to changes to the information item, responding to the notice describing changes to the information item in a manner prescribed by the first program segment included within that program entity.

8. The method of claim 7, wherein each program entity includes second program segment governing how that program entity will respond to said synchronization notice, comprising the further steps of:

receiving the synchronization notice at a program entity having a same identifier as the information item changed at the one site; and

responding to the synchronization notice in a manner prescribed by the second program segment included within that program entity.

9. The method of claim 3, wherein program entities are allowed to cancel subscriptions to changes to any information item, comprising the further step of:

deleting registration of a program entity that previously subscribed to changes to a particular information item but later cancelled its subscription to changes to the information item.

10. The method of claim 9, comprising the further step of deleting an information item from the first database portion.

11. The method of claim 10, wherein an information item is deleted only after any previous subscriptions to changes in that information item have been cancelled.