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

[Jud Spencer]

On 11/11/05 10:59:48 AM, "Nick Zitzmann" <nick at chronosnet.com> wrote:

> 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...

OK, but why were you refusing the delete changes if they were irrelevant?
Just accept them and the problem goes away. I was under the impression that
there was no good reason to refuse a delete. It's not going to cascade
further as a result.