Comments on: slow sync and transparent behaviour http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/ Google and Zimbra contact sync for Thunderbird. Sat, 04 Feb 2012 03:04:53 +0000 http://wordpress.org/?v=2.5.1 By: Librada Ritchko http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1690 Librada Ritchko Fri, 29 Apr 2011 14:56:17 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1690 There is obviously a bundle to realize about this. I feel you made certain good points in features also. There is obviously a bundle to realize about this. I feel you made certain good points in features also.

]]> By: mfc http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1551 mfc Sat, 14 Aug 2010 13:14:12 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1551 Leni Just to let you know, have been using zindus intensively now for >3 mths. Absolutely no problems. Despite G's recent adding of surname/firstname fields (a few days ago) which could have created chaos. thanks mc Leni

Just to let you know, have been using zindus intensively now for >3 mths. Absolutely no problems.
Despite G’s recent adding of surname/firstname fields (a few days ago)
which could have created chaos.
thanks
mc

]]> By: leni http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1121 leni Sat, 01 May 2010 01:12:18 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1121 @mfc, just FYI, release 0.8.16 of the addon will remove extensions.zindus preferences on uninstall. Thanks for pointing that out! @mfc, just FYI, release 0.8.16 of the addon will remove extensions.zindus preferences on uninstall. Thanks for pointing that out!

]]> By: mfc http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1097 mfc Thu, 29 Apr 2010 09:02:55 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1097 Leni thanks very much, that is helpful. Better understanding leads to fewer problems (in life as well as software ;-) Leni

thanks very much, that is helpful. Better understanding leads to fewer problems
(in life as well as software ;-)

]]> By: leni http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1096 leni Thu, 29 Apr 2010 08:51:49 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1096 Change detection varies according to the data source: - tb: calculate a checksum on each sync (as you guessed). Change in checksum implies change in contact. - Google: query "all contacts newer than XXX" where XXX is the time of the previous request - Zimbra: query "all contacts newer than XXX" where XXX is a monotically increasing SyncToken Change detection varies according to the data source:
- tb: calculate a checksum on each sync (as you guessed). Change in checksum implies change in contact.
- Google: query “all contacts newer than XXX” where XXX is the time of the previous request
- Zimbra: query “all contacts newer than XXX” where XXX is a monotically increasing SyncToken

]]> By: mfc http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1092 mfc Thu, 29 Apr 2010 07:22:43 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1092 Leni But when you say "When a contact on one side changes, fast sync modifies the contact on the other side by overwriting all the fields that are common to both" they key question is what method does Zindus use to know which side has changed? A simple comparison would just tell it both sides are different, and it seems like it is not keeping a full copy of each Tb record, so eg does it keep (say) a hash of each record or some other method? Apologies I am not a programmer so can't check the source myself to understand. Leni

But when you say “When a contact on one side changes, fast sync modifies the contact on the other side by overwriting all the fields that are common to both” they key question is what method does Zindus use to know which side has changed?

A simple comparison would just tell it both sides are different, and it seems like it is not keeping a full copy of each Tb record, so eg does it keep (say) a hash of each record or some other method? Apologies I am not a programmer so can’t check the source myself to understand.

]]> By: leni http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1091 leni Thu, 29 Apr 2010 07:09:50 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1091 @mfc, the addon only knows that a contact has changed, it doesn't know which field(s) in a contact changed. This text (added to <a href="zindus.com/i/fast-sync" rel="nofollow">fast sync</a>) explains what happens next: When a contact on one side changes, fast sync modifies the contact on the other side by overwriting all the fields that are common to both (and leaving the fields that aren’t common untouched). @mfc, the addon only knows that a contact has changed, it doesn’t know which field(s) in a contact changed.

This text (added to fast sync) explains what happens next:
When a contact on one side changes, fast sync modifies the contact on the other side by overwriting all the fields that are common to both (and leaving the fields that aren’t common untouched).

]]> By: mfc http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1090 mfc Thu, 29 Apr 2010 06:47:50 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1090 Leni eg if a field (say the Work web address) is different between Tb and G, how does it know which is new and which is old (to be overwritten)? Does it keep a snapshot of the Tb addressbook? (seems likely as this is probably one of the functions of slow sync, and a reset might just delete this snapshot) Is there an indicator from G that a field has changed since some event? Leni

eg if a field (say the Work web address) is different between Tb and G, how does it know which is new and which is old (to be overwritten)? Does it keep a snapshot of the Tb addressbook? (seems likely as this is probably one of the functions of slow sync, and a reset might just delete this snapshot) Is there an indicator from G that a field has changed since some event?

]]> By: leni http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1086 leni Thu, 29 Apr 2010 05:37:22 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1086 @mfc, what sort of things need more explanation re: <a href="zindus.com/i/fast-sync" rel="nofollow">fast sync</a>? @mfc, what sort of things need more explanation re: fast sync?

]]> By: mfc http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1085 mfc Thu, 29 Apr 2010 05:23:04 +0000 http://www.zindus.com/blog/2009/11/06/slow-sync-and-transparent-behaviour/#comment-1085 re 1. I should add I am using Tb 2.0.0.24, which in a csv puts the Work url in Web Page 1 and the Home url in Web Page 2. G them imports them both as Home Page. re 1. I should add I am using Tb 2.0.0.24, which in a csv puts the Work url in Web Page 1 and the Home url in Web Page 2. G them imports them both as Home Page.

]]>