Update README

Author: Michael Shannon Potter

README.md

@@ -31,6 +31,7 @@ A significant burden on performance for graphics-rich applications like [Path](h
 - [**1.0**](https://github.com/path/FastImageCache/releases/tag/1.0)   (10/18/2013): Initial release
 - [**1.1**](https://github.com/path/FastImageCache/releases/tag/1.1)   (10/22/2013): Added ARC support and more robust Core Animation byte alignment
 - [**1.2**](https://github.com/path/FastImageCache/releases/tag/1.2)   (10/30/2013): Added support for image format styles and canceling image requests
+- [**1.3**](https://github.com/path/FastImageCache/releases/tag/1.3)   (03/30/2014): Significant bug fixes and performance improvements.
 
 ## What Fast Image Cache Does
 
@@ -128,6 +129,12 @@ For example, if an original image is resized by an entity to create a thumbnail
 
 Image format families can be specified to efficiently make use of a single source image. See [Working with Image Format Families](#working-with-image-format-families) for more information.
 
+### Data Protection
+
+In iOS 4, Apple introduced data protection. When a user's device is locked or turned off, the disk is encrypted. Files written to disk are protected by default, although applications can manually specify the data protection mode for each file it manages. With the advent of new background modes in iOS 7, applications can now execute in the background briefly even while the device is locked. As a result, data protection can cause issues if applications attempt to access files that are encrypted.
+
+Fast Image Cache lets your specify the data protection mode each of its image tables should use. Be aware that enabling data protection for image table files means that Fast Image Cache might not be able to read or write image data from or to these files when the disk is encrypted.
+
 ## Requirements
 
 Fast Image Cache requires iOS 6.0 or greater and relies on the following frameworks:
@@ -166,13 +173,18 @@ Before the image cache can be used, it needs to be configured. This must occur e
 Each image format corresponds to an image table that the image cache will use. Image formats that can use the same source image to render the images they store in their image tables should belong to the same [image format family](#working-with-image-format-families). See [Image Table Size](#image-table-size) for more information about how to determine an appropriate maximum count.
 
 ```objective-c
+static NSString *XXImageFormatNameUserThumbnailSmall = @"com.mycompany.myapp.XXImageFormatNameUserThumbnailSmall";
+static NSString *XXImageFormatNameUserThumbnailMedium = @"com.mycompany.myapp.XXImageFormatNameUserThumbnailMedium";
+static NSString *XXImageFormatFamilyUserThumbnails = @"com.mycompany.myapp.XXImageFormatFamilyUserThumbnails";
+
 FICImageFormat *smallUserThumbnailImageFormat = [[FICImageFormat alloc] init];
 smallUserThumbnailImageFormat.name = XXImageFormatNameUserThumbnailSmall;
 smallUserThumbnailImageFormat.family = XXImageFormatFamilyUserThumbnails;
 smallUserThumbnailImageFormat.style = FICImageFormatStyle16BitBGR;
 smallUserThumbnailImageFormat.imageSize = CGSizeMake(50, 50);
 smallUserThumbnailImageFormat.maximumCount = 250;
 smallUserThumbnailImageFormat.devices = FICImageFormatDevicePhone;
+smallUserThumbnailImageFormat.protectionMode = FICImageFormatProtectionModeNone;
 
 FICImageFormat *mediumUserThumbnailImageFormat = [[FICImageFormat alloc] init];
 mediumUserThumbnailImageFormat.name = XXImageFormatNameUserThumbnailMedium;
@@ -181,6 +193,7 @@ mediumUserThumbnailImageFormat.style = FICImageFormatStyle32BitBGRA;
 mediumUserThumbnailImageFormat.imageSize = CGSizeMake(100, 100);
 mediumUserThumbnailImageFormat.maximumCount = 250;
 mediumUserThumbnailImageFormat.devices = FICImageFormatDevicePhone;
+mediumUserThumbnailImageFormat.protectionMode = FICImageFormatProtectionModeNone;
 
 NSArray *imageFormats = @[smallUserThumbnailImageFormat, mediumUserThumbnailImageFormat];
 ```