ios developer tiny share-20161027

今天讲Objective-C的持久化对象，你需要实现NSCoding协议，另外，一些集合类，比如NSArray, NSDictionary, NSString, NSData, NSDate and NSNumber，已经实现了这个协议，意味着这些类已经支持持久化。

下面是ios官方api的文档：

Use Collections to Persist Your Object Graph

The NSArray and NSDictionary classes make it easy to write their contents directly to disk, like this:

NSURL *fileURL = ...
NSArray *array = @[@"first", @"second", @"third"];

BOOL success = [array writeToURL:fileURL atomically:YES];
if (!success) {
	// an error occured...
}

If every contained object is one of the property list types (NSArray, NSDictionary, NSString, NSData, NSDate and NSNumber), it’s possible to recreate the entire hierarchy from disk, like this:

NSURL *fileURL = ...
NSArray *array = [NSArray arrayWithContentsOfURL:fileURL];
if (!array) {
	// an error occurred...
}

For more information on property lists, see Property List Programming Guide.

If you need to persist other types of objects than just the standard property list classes shown above, you can use an archiver object, such as NSKeyedArchiver, to create an archive of the collected objects.

The only requirement to create an archive is that each object must support the NSCoding protocol. This means that each object must know how to encode itself to an archive (by implementing the encodeWithCoder: method) and decode itself when read from an existing archive (the initWithCoder: method).

The NSArray, NSSet and NSDictionary classes, and their mutable subclasses, all support NSCoding, which means you can persist complex hierarchies of objects using an archiver. If you use Interface Builder to lay out windows and views, for example, the resulting nib file is just an archive of the object hierarchy that you’ve created visually. At runtime, the nib file is unarchived to a hierarchy of objects using the relevant classes.

For more information on Archives, see Archives and Serializations Programming Guide.