AwesomeCache Versions Save

Compatibility for Swift 3.0

• Add support for Swift 2.3

Fixes a bug that would lead to a crash if a new cache is created with the NSFileProtection option (Thanks @niklassaers)

AwesomeCache 3 is designed to have a sync API, making it easy to reason about the actual contents of the cache. This decision has been made based on feedback from the community, to keep the API of AwesomeCache small and easy to use.

The internals of the cache use a concurrent dispatch queue, that syncs reads and writes for thread safety. In case a particular caching operation blocks your main thread for too long, consider offloading the read and write operations to a different thread.

dispatch_async(dispatch_get_global_queue(DISPATCH_QUEUE_PRIORITY_DEFAULT, 0)) {
    cache["name"] = "Alex"
}

Further improvements

• Added a new way to return an expired object in objectForKey: if present (#31)
• Adds a way to set the NSFileProtectionKey value on the internal NSFileManager. This may be necessary in case you observe odd behaviour when accessing the cache in the background. (#64)
• Adds a new method to get allObjects from the cache (optionally, expired objects may be queried as well)

• An Obj-C NSKeyedUnarchiver was added since it can throw exceptions which can't be caught in Swift (Thanks @JaviSoto)
• Use a concurrent queue to allow multiple simultaneous reads from the cache. (Thanks @JaviSoto)

• Support for watchOS
• Support for tvOS

• Support for Swift 2
• Updated documentation
• Changes the internal implementation to use the new NSURL APIs instead of paths

• fixes a deadlock in objectForKey (thanks @alenofx)
• keys are now sanitized to make sure the file system is able to persist the cache object

🚀

Rename AwesomeCache class to Cache. (It is still as awesome as before. ✨)