Learning Core Data for iOS: A Hands-On Guide to Building Core Data Applications

Introducing Faulter

The process of generating thumbnails will impact a potentially large number of objects. Any time a large number of objects are processed, care should be taken to ensure memory bloating and interface lag is avoided. As explained in Chapter 10, you should turn objects into faults once you’re finished with them using refreshObject:mergeChanges:NO after saving the containing context. With a parent and child context hierarchy, you’ll need to do this for every context in the hierarchy. That means for every object imported, a save and fault are required in all three contexts.

The process of saving a context and turning a particular object into a fault is a repeatable one. The code needed to perform this task can be reused regardless ...