Determining priority between data items

Abstract

One embodiment of the present invention enables nodes or endpoints involved with synchronization of data items to determine which version of a data item (if any) has priority over another version of that same data item. Within the present embodiment, when a data item Is modified by a node, it is presumed that the modified data item takes priority aver the previous version of that data item. Therefore, the “descendant” data item (modified) takes precedence over its “ancestor” data item (previous version). By including this type of “pedigree” information with data items involved with synchronization between different nodes or endpoints, the present embodiment enables the endpoints to determine which version of a data item (if any) has priority over another version of that same data item.

Description

CROSS REFERENCE TO RELATED APPLICATIONS [0001] This application is a continuation application of application Ser. No. 10 / 159,461, entitled “DETERMINING PRIORITY BETWEEN DATA ITEMS,” filed May 31, 2002, now allowed, which claims priority to Provisional Application Ser. No. 60 / 377,713, entitled “SYSTEM AND METHOD FOR SYNCHRONIZING COMPUTER DATABASES,” filed May 2, 2002. The subject matter in the above-identified co-pending and commonly owned application(s) is incorporated herein by reference.TECHNICAL FIELD [0002] The present invention relates generally to the field of databases. Specifically, the present invention relates to the field of synchronizing data between multiple nodes. BACKGROUND ART [0003] In the realm of handheld computer systems (commonly referred to as personal digital assistants or PDAs), it is not uncommon for a data set to exist and be maintained both on the PDA and on at least one other computing device. For example, a user may maintain a calendar or address book o...

AI Technical Summary

Benefits of technology

[0012] Accordingly, given that different versions of the same record may reach a node, a need exists for a method and / or system that enables the node to more easily determine which version of the record (if any) takes precedence over the others. The present invention provides one or more embodiments which accomplish the above mentioned need.

[0013] Specifically, one embodiment of the present invention enables nodes or endpoints involved with synchronization of data items to determine which version of a data item (if any) has priority over another version of that same data item. Within the present embodiment, when a data item is modified by a node, it is presumed that the modified data item takes priority over the previous version of that data item. Therefore, the “descendant” data item (modified) takes precedence over its “ancestor” data item (previous version). By including this type of “pedigree” information with data items involved with synchronization between different nodes or endpoints, the present embodiment enables the endpoints to determine which version of a data item (if any) has priority over another version of that same data item.

[0016] In still another embodiment, the present invention includes a computer-usable medium having computer-readable code embodied therein for causing a computing device to perform particular operations. The computer-usable medium causes the computing device to perform: deciding if a first and second data items have matching identities during a synchronization process between two nodes; deciding if the content of the first and second data items are unequal; deciding if the first data item descended from the second data item, in response to the first and second data items having matching identities and the content of the first and second data items being unequal; and deciding that the first data item has priority over the second data item, in response to the first data item descending from the second data item.

Problems solved by technology

Consequently, the records on the PDA that have changed cannot be identified using the dirty bits.

Thus, one problem with the common synchronization techniques is that slow syncs are occurring more frequently as a growing number of people interact with multiple computer systems with their PDA.

Slow syncs take longer to complete than fast syncs, and so they are less desirable.

Another issue with typical synchronization techniques is that they are limited with respect to the different types of syncs that can now occur.

However, the paradigm in which the PDA serves in essence as the nexus between the user's home and office computer systems is not as applicable as it once was.

As a result, different versions of the same record may reach a node, causing a conflict to arise as to which version of the record should take precedence over another.

Using contemporary synchronization techniques, these records are unnecessarily replicated at the destination node, slowing down syncs while consuming memory.

Images