maxCacheSize option about node-cache HOT 8 CLOSED

I think instead of throwing error, it should remove the oldest entry in cache and accommodate the new entry. Having a fixed size for cache is to limit the memory usage, and cache being full isn't really an error scenario.

Just started using this library in a project, and saw this flag in the docs.

from node-cache.

We currently regard sophisticated expiry logic like that as to big for that project :(

from node-cache.

Thanks!
This is a nice idea.
I add it to the TODO list and will have a look at it until there is some time ;-)

from node-cache.

This has landed in pr #141
Will be part of v5.0

from node-cache.

This would be GREAT!
Up.

from node-cache.

@erdii You used "currently" in your answer around a year ago, so I am asking again about #63 (comment) :)

from node-cache.

up. Evicting oldest key is the best option. Or at least allow us to catch such error using event handling so that we can do that ourselves

from node-cache.

@daluf will take care of this

from node-cache.