You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is intended behaviour. Up to version 2.5.0 setting maxAge caused removal of item from cache after maxAge milliseconds. At the moment the check is not made against total age of item but against its last access date.
This means that cached item can be stored indefinately if they are accessed often. Item will be removed only if it's accessed after time greater than maxAge.
Is this intended behaviour? If it is it should be made clear in the documentation.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is intended behaviour. Up to version 2.5.0 setting maxAge caused removal of item from cache after maxAge milliseconds. At the moment the check is not made against total age of item but against its last access date.
This means that cached item can be stored indefinately if they are accessed often. Item will be removed only if it's accessed after time greater than maxAge.
Is this intended behaviour? If it is it should be made clear in the documentation.
The text was updated successfully, but these errors were encountered: