Why doesn't bigcache consider designing expiration time for each cache key?
Ouverte
question
- Langage dominant
- Go
- Étoiles
- 8.2k
- Forks
- 614
- Merge moyen
- 5 j 12 h
- PR mergées (30 j)
- 1
Description
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?
Guide de contribution
Aucun guide de contribution indexé pour ce dépôt
Évaluation
Cette issue n'a pas encore été évaluée.