Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better invalidation handling #1

Open
Aaron-P opened this issue Oct 28, 2014 · 1 comment
Open

Better invalidation handling #1

Aaron-P opened this issue Oct 28, 2014 · 1 comment

Comments

@Aaron-P
Copy link
Member

Aaron-P commented Oct 28, 2014

If a cache key is invalidated from under an info call for example, we should try to give a better error than 'doesn't exist'.

@Aaron-P
Copy link
Member Author

Aaron-P commented Nov 12, 2014

I'm not sure what other sort of behavior we can have for this, any ideas @IDisposable? A possibility would be to keep track of the expiration time of the entry in javascript and show a different warning if they try to get details for an expired key if we expected it to be expired.

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

No branches or pull requests

1 participant