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

feature suggestion: add a callback for expired entries #60

Open
lamemind opened this issue Mar 10, 2016 · 2 comments
Open

feature suggestion: add a callback for expired entries #60

lamemind opened this issue Mar 10, 2016 · 2 comments

Comments

@lamemind
Copy link

Hello,

At this precise moment, I'd really love a callback called just before (or right after) an entry expires.

Thanks

@robertpallas
Copy link
Contributor

There is timeout callback, undocumented.

It runs after the key is deleted without sending the value into it. One of the 2 should be available:

  • (preferably) sending both the key and the value to the callback
  • running delete after callback so that the value could be accessed from the cache

Thoughts @ptarjan?

@ptarjan
Copy link
Owner

ptarjan commented Jun 7, 2016

I like it happening after the delete since the notion of a callback is to tell you once it is done. Is be open to adding the value if you send a PR (and add it to the docs :))

Sent from my iPhone

On Jun 7, 2016, at 7:14 AM, Robert Pallas [email protected] wrote:

There is timeout callback, undocumented.

It runs after the key is deleted without sending the value into it. One of the 2 should be available:

(preferably) sending both the key and the value to the callback
running delete after callback so that the value could be accessed from the cache
Thoughts @ptarjan?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

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

No branches or pull requests

3 participants