-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
RFC: Root Query TTL #1480
Comments
Sounds like: #41 I think this would be really cool to have after 1.0, we probably don't want to do it before then because it will require some store changes. But we could start working on designs now! |
Yeah agreed. I think we should take #1432 into account when talking about this, though, as there would likely need to be some sort of function on the storage interface that |
My use case involves a complex SPA, running full screen for long periods of time (multiple days). To prevent the store from ballooning, I've implemented a simple renderless component which will call Ugly, but it does the job : https://gist.github.com/kouak/18910729ecfda906eadbd6084793f5eb |
I'm closing this, please refer to #621 for updates on this topic |
Hey guys,
I was thinking that perhaps a decent solution for the "ever expanding cache" problem might be to allow for a configurable TTL on root queries. This TTL value could reset whenever the query is updated. Whenever the query goes stagnant beyond a certain period, it could simply be purged out of the store once it's subscriber count reaches zero. Any store entries that are orphaned (you can no longer traverse references from the entry to a root query) would also be purged. Thoughts?
The text was updated successfully, but these errors were encountered: