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

staleTimeout for first request should returns null if no data at timeout time #68

rockbot opened this issue Jul 10, 2014 · 0 comments


Copy link

@rockbot rockbot commented Jul 10, 2014

Right now, with staleTimeout, if it takes a ridiculously long time to get data (which will be added to the cache after it's been loaded) on the very first request, the whole process blocks until that data is loaded. Once it's stored in the cache, of course everything is fine.

I'd really love to have a situation where even if there's no data, the cache returns null after a designated timeout, but then continues to load in the background. This way we can keep the user moving with slightly less data and then show the data when it finally arrives.

@hueniverse hueniverse added this to the 3.0.1 milestone Aug 2, 2014
@hueniverse hueniverse added enhancement and removed enhancement labels Aug 2, 2014
@hueniverse hueniverse self-assigned this Aug 2, 2014
@hueniverse hueniverse changed the title staleTimeout for first ever request should (returns null if no data at timeout time) staleTimeout for first request should returns null if no data at timeout time Aug 2, 2014
@hueniverse hueniverse closed this in ab4e604 Aug 3, 2014
@Marsup Marsup added feature and removed request labels Sep 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.