All Versions
9
Latest Version
Avg Release Cycle
74 days
Latest Release
2913 days ago
Changelog History
Changelog History
-
v4.0 Changes
September 18, 2016- โ Add support for Swift 2.3
-
v3.0.1 Changes
June 27, 2016๐ Fixes a bug that would lead to a crash if a new cache is created with the
NSFileProtection
option (Thanks @niklassaers) -
v3.0 Changes
June 03, 2016๐ 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 internalNSFileManager
. 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)
- โ Added a new way to return an expired object in
-
v2.2 Changes
May 27, 2016 -
v2.1 Changes
March 21, 2016- ๐ Support for watchOS
- ๐ Support for tvOS
-
v2.0 Changes
October 17, 2015- ๐ Support for Swift 2
- ๐ Updated documentation
- ๐ Changes the internal implementation to use the new
NSURL
APIs instead of paths
-
v1.1
March 24, 2015 -
v1.0.2 Changes
July 09, 2015- ๐ fixes a deadlock in
objectForKey
(thanks @alenofx) - keys are now sanitized to make sure the file system is able to persist the cache object
- ๐ fixes a deadlock in
-
v1.0.1 Changes
March 24, 2015๐ฑ ๐