allegro / allegro/bigcache

Why doesn't bigcache consider designing expiration time for each cache key?

Abierto
#360 4 comentarios 2 reacciones 0 asignados Ver en GitHub
question
Lenguaje dominante
Go
Estrellas
8.2k
Forks
614
Merge medio
5 d 12 h
PR fusionados (30 d)
1

Descripción

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?

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.