-
Notifications
You must be signed in to change notification settings - Fork 74
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
Cache doesn't seem to work #18
Comments
Thank you for submitting issue! Did you tried this with different endpoint? Maybe there is some problem related to big size of your response and WebSQL. I will try to debug it, but maybe it will tooks me weeks or two... You can also try this code:
|
Yes, I also tried it with other endpoints. Some of the endpoints return a quite large dataset (like the example above), but there are also endpoints which return a small dataset (f.e. 1 record). |
Maybe its releated to #17 Did you tried older version? Can you try version before apostrophe fix? And what about Chrome or other browsers? I will try to investigate problem myself soon as possible. |
Can you test latest version? |
Should be fixed in latest version. |
Hello, I've implemented the cache service like in the documentation in this repo.
But when I try to reopen the page in my app several times, it's continuesly making a new http request instead of returning the cached data.
When I try to inspect my app with Safari I see that it's building a cache in the database under "Storage", but when trying to view the data Safari is not responding anymore and I have to restart Safari again.
Am I doing something wrong?
The same request for several times in a few seconds. The time to load the response is getting worse instead of better when reloading the page.
The text was updated successfully, but these errors were encountered: