Hi, I don't know if you've ever noticed, but you should have seen that almost immediately after making a change in iCal or Address Book, Spanning Sync would begin to sync. It wouldn't matter if you were an hour away from your scheduled sync interval or not. This is called a trickle sync. Basically, whenever Apple Sync Services detects a change, it forces all sync clients to initiate a sync. It's actually Apple Sync Services that initiates the sync process, not Spanning Sync, but, since Spanning Sync has trickle sync enabled by default, it goes along with the sync initiation.
The problem is that Apple Sync Services is way too overzealous as to when it initiates the trickle sync. In your case it's doing it before you've even finished modifying the event and this causes duplicates. By disabling trickle sync (for Spanning Sync only) using that terminal command, Spanning Sync no longer listens to this trickle sync request from Sync Services and the duplicate is avoided. You will be forced to keep to your scheduled sync interval, and won't pick up changes almost immediately, but you also won't have to deal with the duplicate events. I hope that makes sense. -Byron --- Byron Shaheen [email protected] http://spanningsync.com On Nov 24, 7:37 pm, monkeyspeace <[email protected]> wrote: > That sounds brilliantly close to an accurate description. I'll try > that command. I'm presuming that I need to do it to all 6 user sides? > I'm comfortable enough with Terminal. But, for my education, could you > describe trickle syncing and what this command does? Or, you could > refer me to an article. It's not that I doubt, I just like full > understanding. > > Regardless, this could be a huge help. Thank you! > > J > > On Nov 24, 6:08 pm, "byron.shaheen" <[email protected]> wrote: > > > > > Hi, > > > It's possible that iCal is syncing new events before you're done > > editing them, which can cause a duplicate. To prevent this from > > happening, you can turn off trickle syncing in Spanning Sync by > > copying and pasting the below line into a Terminal window (located in > > the Utilities folder): > > > defaults write com.spanningsync noTrickleSyncing -bool YES > > > Be sure to hit 'return' after pasting the line into the window. > > > Please let us know if that doesn't address the problem or you have > > other questions. > > > Thanks, > > > Byron > > > --- > > Byron Shaheen > > [email protected]http://spanningsync.com > > > On Nov 24, 4:49 pm, monkeyspeace <[email protected]> wrote: > > > > I originally tested SS for the trial period. The setup was: > > > > 1 user side on an iMac > > > 1 user side on a MacBook > > > 1 iPhone > > > > Everything went quite well. That was my testing environment. Upon > > > success there, I amped it up to my real setting. The real setting was: > > > > 2 user sides on an iMac > > > 2 user sides on a MacBook Pro > > > 2 user sides on another MacBook Pro > > > 2 Android phones > > > > All of these locations needed the same calendar data. I wiped all > > > syncing data clear in all devices, and all calendars were clean. SS > > > was installed to handle all of the calendar data for all 8 locations. > > > Almost immediately SS did a poor job. > > > > There is a single, consistent bug that we simply cannot rid of. When > > > entering calendar data on any of the user sides, sometimes that data > > > will somehow localize: it will exist as a double event on that > > > machine, and either not sync or sync as a ghost. If I go to the google > > > web calendar and delete the event, that delete action will not sync > > > through to the machine the event was made on. Or, if there are two > > > copies of the event on that machine (a result of some error), it will > > > delete the event data taht was pushed back through from google > > > servers, but not the original. It seems to only happen if we are > > > entering a couple of events at once, of if SS engages in the middle of > > > editing calendar data. > > > > This is going to make SS prohibitive to use. We did everything correct > > > in set-up. This is an application bug, and I really don't want to have > > > to go through the process of getting our money back. We really do want > > > the service to work. -- You received this message because you are subscribed to the Google Groups "Spanning Sync" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spanningsync?hl=en.
