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

[Nick Zitzmann]

On Nov 11, 2005, at 10:58 AM, Jud Spencer wrote:

>> I'm thinking of changing my client so that it only refuses add &
>> modify changes, while delete changes that would normally be refused
>> are actually marked as accepted. That would work around the problem
>> for now, unless I'm missing something...
>
> Why would you refuse a delete?

The sync client description uses many entities with cascading one-to- 
many relationships, and when the engine pushes a delete change for a  
parent instance of an entity, previously it was refusing the delete  
changes on the child entities that were now irrelevant. But since - 
clientRefusedChangesForRecordWithIdentifier: apparently does nothing,  
it was getting bombarded with delete changes that were previously  
refused, which made sync sessions slower (and call histories longer)  
as more objects were deleted. That's why I originally brought this up...

Nick Zitzmann
<http://www.chronosnet.com/>