Skip to content

Releases: enormego/EGOCache

v2.2.0

14 Oct 21:55
Compare
Choose a tag to compare
  • Setup project/frameworks for Carthage
  • Fixed issues on macOS

v2.1.3

14 Oct 21:39
Compare
Choose a tag to compare

Convert nullability to latest syntax

v2.1.2

14 Oct 21:39
Compare
Choose a tag to compare
  • A little tidying up
  • Audited header for nullability

v2.1.1

14 Oct 21:38
Compare
Choose a tag to compare
  • replace all '/' symbols to '_' in cache key
  • Updating deprecated API for properyListFromData

v2.1

14 Oct 21:37
Compare
Choose a tag to compare
  • Added missing UIKit import
  • Removed autorelease usage
  • Make the defaultTimeoutInterval apply to all caches, not just the global one
  • Added podspec/license
  • fixed a _diskQueue's priority
  • Add dateForKey and allKeys methods

2.0.0

14 Oct 21:33
Compare
Choose a tag to compare

The public interface in 2.0 is largely the same, with the exception of [EGOCache currentCache] being deprecated in favor of [EGOCache globalCache]. You can now create your own instances of EGOCache and tell it to store wherever, this can be good for dividing up caches in different sections of your app.

Internally, EGOCache was largely rewritten to take advantage of libdispatch and is far more stable/performant when handling saves from multiple threads than it was in the past.

One other notable internal change for users upgrading from 1.0 to be aware of, is UIImage's are no longer stored via UIImagePNGRepresentation. They're stored now by archiving UIImage itself, which allows us to retain information such as image scale, orientation, and also store the image in it's native type, so JPEG's are no longer inflated to PNG sizes. If you were previously saving images via setImage:forKey:, but for some reason retrieving them via dataForKey:, you'll need to update your code to account for this.