-
Notifications
You must be signed in to change notification settings - Fork 411
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
Time To Live #18
Comments
This is a very good idea. I don't know if it is possible but I'll think about how to implement this. |
I've tinkered with something like this :
|
Yes that looks promising but how would you handle a TTL greater than the runtime of the app? |
Correct, Also I'm not sure this approach is the best when you have a huge numbers of keys ... Completers would resume on the diff time now and previously calculated expiration timestamps. |
I agree...
Could you please explain that? I don't understand what you mean exactly. |
I'm going to close this for now. I think a external solution would be easier to implement... |
I'd like to use Hive as a temporary cache for resources.
Setup would be done with a TTL field that can be set at the Box and write method level.
box.putAll({'key1': 'value1', 42: 'life'}, ttl: const Duration(seconds:30))
Is this a feature in the scope of Hive ?
Thanks
The text was updated successfully, but these errors were encountered: