Skip to content
This repository has been archived by the owner on Jul 27, 2022. It is now read-only.

Support cache ttl in standalone mode #9

Open
Faklusha opened this issue Sep 8, 2016 · 2 comments
Open

Support cache ttl in standalone mode #9

Faklusha opened this issue Sep 8, 2016 · 2 comments

Comments

@Faklusha
Copy link

Faklusha commented Sep 8, 2016

Hello,

I'm using the cache API via "apigee-access".

I found a problem that in standalone mode the 'ttl' doesn't work. I see in sources of "apigee-access" that for standalone mode the simple object is used as a data storage. It is a cause why cache 'ttl' doesn't work. Is it possible to support 'ttl' for standalone mode? May be to use 'volos-cache-memory' in standalone mode instead of simple object?

Thank you,
Yuliana Sukonka

@confuser
Copy link

@theganyo Could this be looked into? We're having a few unit tests failing due to this.

@theganyo
Copy link
Member

Could you potentially just use volos-cache-apigee? It has exactly what you're looking for: A "fallback" configuration option to automatically fallback to another cache (eg. volos-cache-memory).

(see also: https://github.com/apigee-127/volos/blob/master/cache/apigee/lib/cache.js#L32)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants