Disk
Cache
| Disk | Cache | |
|---|---|---|
| - | 2 | |
| 3,110 | 2,997 | |
| - | 0.7% | |
| 3.9 | 6.9 | |
| 5 months ago | 5 months ago | |
| Swift | Swift | |
| MIT License | NOASSERTION |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Disk
We haven't tracked posts mentioning Disk yet.
Tracking mentions began in Dec 2020.
Cache
- Trouble building for ios device
-
SwiftUI jobs with low compensation?
For data storage, we have a caching layer that receives data from the cloud and stores it both in memory and on device. Then there is a pub model that notifies listeners when the data has been updated. it's pretty simple but works great! I like hyperoslo's implementation for cache: https://github.com/hyperoslo/Cache For units, we just build a protocol for the internet piece and provide the data locally. We cache the unit test data in a different folder on device and it all works seamlessly. I think the hardest part there was intercepting the HTTP requests and forking to the local test data. The key there was implementing a URLProtocol subclass.
What are some alternatives?
YYCache - High performance cache framework for iOS.
RocketData - A caching and consistency solution for immutable models.
HanekeSwift - A lightweight generic cache for iOS written in Swift with extra love for images.
Carlos - A simple but flexible cache
MGCacheManager - A delightful iOS and OS X Networking Cache Managing Class
CoreXLSX - Excel spreadsheet (XLSX) format parser written in pure Swift
Track - Track is a thread safe cache write by Swift. Composed of DiskCache and MemoryCache which support LRU.
Dollar - A functional tool-belt for Swift Language similar to Lo-Dash or Underscore.js in Javascript
SPTPersistentCache - Everyone tries to implement a cache at some point in their iOS app’s lifecycle, and this is ours.