eelfner / coredatasafeexample Goto Github PK

Sorry, no way to comment in the code :/

This should not need to be synchronous. Once the private moc has saved to the main we really don't care when the moc writes. It can be now or can be later. It only matters if we crash and that is not the responsibility of the private moc imho.

Kick off an async or don't include the propagated save at all. Just because a child is done doesn't mean it is a good time to halt the UI to write.

I would recommend never using sync here. It is just asking for pain down the road.

This should be async and the UI must wait for the persistence layer to be ready. Normally this is < 100ms and not noticeable by the UI. But when a merge or some other long task runs the UI must be able to handle it. Plan for it and when it happens it is not an issue. Don't plan for it and you are asking for a re-write in the future.