[sync-services-developers] Sync Services not taking "no" for an answer?

[Brian M. Criscuolo]

Nick,

Welcome to the changes in Sync Services brought on with 10.4.3!

This didn't happen before the update, and it does now. Records that  
have been refused are now being pushed every time for me as well - in  
a shipping product! Its driving me absolutely crazy. In my case, I  
refused records (events) from a read-only calendar. The calendar has  
not been refreshed, so the events haven't changed.

I guess both you and I should submit this to Apple so that they can  
get it fixed at some point. For now, I've taken to storing an array  
of refused records in the client data and checking each one against  
that. Totally sucks.

There are some folks from Apple on this list - would any care to  
elaborate on the various changes in Sync Services with the 10.4.3  
update? We really need to know what has been changed.

b

On Nov 10, 2005, at 11:53 AM, Nick Zitzmann wrote:

> I noticed recently that my sync client lately has been taking an  
> abnormally long amount of time to complete its work, almost as if  
> the sync client was performing a slow sync every single time. So I  
> took a look at the call history in Syncrospector, and it was  
> performing a fast sync, but the sync client was continuously  
> pulling changes that the client refused earlier, and these changes  
> are delete changes that have not been modified between sessions.  
> Two back-to-back call histories show that the sync client rejected  
> the same change twice, but Sync Services keeps pushing it.
>
> All that the sync client is doing is:
> 1. Taking the change obtained from the change enumerator
> 2. Calling -clientRefusedChangesForRecordWithIdentifier: with the  
> sync client's version of the record identifier (which was taken  
> from the change from #1)
> 3. After taking in all changes from all of the change enumerators,  
> calling -clientCommittedAcceptedChanges, followed by -finishSyncing
>
> According to the documentation, that should be all, but apparently  
> it's not. It doesn't pull committed changes twice, so why is it  
> pulling refused changes twice? Has anyone else seen this before,  
> and if so, what did you do to get Sync Services to take "no" for an  
> answer?
>
> Nick Zitzmann
> <http://www.chronosnet.com/>
>
>
> _______________________________________________
> sync-services-developers mailing list
> sync-services-developers at lists.markspace.com
> http://lists.markspace.com/mailman/listinfo/sync-services-developers


********************
Brian M. Criscuolo
Senior Software Engineer
Mark/Space, Inc.
bcriscuolo at markspace.com
<http://www.markspace.com>