-- Eric Hildum
> From: Bill Cheeseman <[EMAIL PROTECTED]> > > 1. What exactly is "Synchronize" supposed to do in the case of missing > items? (For example, if an item exists on one machine but not the other, > does it always create a matching item on the machine where the item is > missing -- and never delete the item on the machine where the item exists? > This would represent a bias in favor of existing items that ought to be > spelled out in the documentation. Or is it supposed to depend on which > machine was used more recently than the last sync? Or what?) If the item has been added to one machine, then the sync will add it to the other. If the item had existed on both machines previously, and was deleted from one, it will be deleted from the other. > > 2. What exactly is "Synchronize" supposed to do in the case of edited items? > (A bias in favor of existing items doesn't help, here. How are "conflicts" > resolved?) Usually, both devices will have two copies of the edited items after the sync, with each set of edits. You can merge the two by hand, or in the case of contacts, with my Merge Contacts script (if it ever got posted to Applescriptcentral). > > 3. What exactly are the two directional settings supposed to do? (For > example, if an item exists on the destination machine but not the source > machine, does it delete the item on the destination machine? If two items > have the same name but differ in content, does the designated source always > replace the designated destination?) The destination options change the sync to a copy. The existing data on the destination is erased, and a copy of the source machines data is made to the destination device. In some situations, this is very useful (for example, when connecting the Palm to more than one machine). > > 4. How does the conduit decide if items are the same or different? By name > only? I don't have all the details, but there is a flag (and maybe a timestamp) in each record to indicate if it has been edited or deleted since the last sync. This is used in normal synchronization. In the slow sync case, all the records are compared to identify changes. > > I'm used to file synchronization utilities that explain how they work (for > example, how "conflicts" are resolved), so that I can design my own usage > patterns with confidence. The Entourage conduit leaves me guessing. The Entourage conduit is the same as all the other Palm conduits as far as I can tell. It seems to be pretty good about resolving conflicts in a way that does not lose data. For example, if you edit a record on one device and delete it on the other, the edited record will be made available on both devices. -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
