Why doesn't bigcache consider designing expiration time for each cache key?
Offen
question
- Vorherrschende Sprache
- Go
- Sterne
- 8.2k
- Forks
- 614
- Ø Merge
- 5 T. 12 Std.
- Gemergte PRs (30 T.)
- 1
Beschreibung
During the process of using and reading the source code, it was found that in each instance of bigcache, all key-value pairs can only be set with a unified expiration time. A `time.Ticker` is used to periodically check if the cache has expired based on the interval set by `CleanWindow`. So why wasn't a method considered to allow setting expiration time for each cache key?
Beitragsleitfaden
Für dieses Repository ist kein Beitragsleitfaden indexiert
Bewertung
Dieses Issue wurde noch nicht bewertet.