jmdobry
commented
8 years ago | Feature | $cacheFactory | angular-cache |
|---|---|---|
| core implementation usable outside of Angular | no | yes |
| key/value store | yes | yes |
| in-memory support | yes | yes |
| localStorage support | no | yes |
| sessionStorage support | no | yes |
| custom storage support | no | yes |
| can set maximum capacity | yes | yes |
| LRU support | yes | yes |
| support for time-based expiration of items | no | yes |
| remove all expired items | n/a | yes |
| "touch" an item | n/a | yes |
| execute callback when an item expires | n/a | yes |
| get info about cache | yes | yes |
| get info about single item | no | yes |
| get item by key | yes | yes |
| remove item by key | yes | yes |
| remove all items | yes | yes |
| get keys of all caches | no | yes |
| clear all caches | no | yes |
| disable/enable a cache | no | yes |
| "touch" all items in all caches | n/a | yes |
| remove expired items from all caches | n/a | yes |
| get all keys in a cache | no | yes |
| clear a cache on a given interval | no | yes |
Closing because I’m not sure this is an issue, if you are convinced that this is really a bug, please feel free to re-open the issue and add more information:
- good - Your versions of Angular, Angular-cache, etc, relevant console logs/error, code examples that revealed the issue
- better - A plnkr, fiddle, or bin that demonstrates the issue
- best - A Pull Request that fixes the issue, including test coverage for the issue and the fix
Otherwise support is done via the mailing list.
janpio
This may seem like a silly question to you, but how and why is this better than Angular's $cacheFactory?